Skip to content

Latest commit

 

History

History
125 lines (77 loc) · 5.54 KB

OSCustomisation.md

File metadata and controls

125 lines (77 loc) · 5.54 KB
Raw

[toc]

Browser Customisation

Firefox

Changing the Ctrl+F (Finder) highlighting colour

  1. Open Firefox.
  2. In the URL (address) bar, type about:config and press the Enter key.
  3. A warning message would turn up, Proceed with Caution. Press the Accept the Risk and Continue button.
  4. In the search bar that turns up in the new page, type ui.textSelectBackgroundAttention.
  5. Change the default value type by clicking on the radio box labelled String.
  6. Then click on the + button on the right hand side to input a HEX colour code (include the # symbol prefix).
  7. That's it! Close the about:config page, and try out Ctrl+F. Your chosen colour should be displayed now :D

Tutorial for creating userChrome styles for Firefox

Since there is no real help or documentation how to style the new Firefox Beta 57 I found a way how to live-debug the userChrome.css file.

Create the userChrome.css

  1. Enable userChrome.css support in Fx v69+
  2. Open about:support
  3. Click on "Profile Folder" -> "Open Folder"
  4. Create a sub-folder named "chrome"
  5. Change into the new folder
  6. Create a file named "userChrome.css"
  7. Add some rules
  8. Restart Firefox

Live-Testing styles

Pre-setup

Before being able to try styles, you need to enable two developer options (only do this once). To do that:

  1. Press Ctrl + Shift + I on Win/Linux or Cmd + Opt + I on Mac
  2. Click on the cog that appears in a right or left top corner, next to other buttons.
  3. Scroll down to Advanced Settings and check the settings "Enable browser chrome and add-on debugging toolboxes" and "Enable remote debugging".
  4. Close the developer tools panel and proceed with next tutorial

Testing a style

  1. Press Ctrl + Alt + Shift + I on Win/Linux or Cmd + Opt + Shift + I on Mac
  2. A permission dialog will prompt you to allow remote debug, accept
  3. Click on the tab Style Editor, choose file userChrome.css on the sidebar
  4. Choose the style you want to preview from this repository, copy the code
  5. Scroll down on the development tools window textbox, paste the code
  6. You should see the style being applied. If you like what you see, you can click Save, otherwise it will disappear after restarting the browser.

Styling Context Menus / Popups

from /u/DanTheMan74 The Firefox dev tools, when they're opened for remote debugging of the browser content, have an extra option that's hidden behind the dropdown at the top right, a thing which many people have no clue about.

The toggle is called Disable Popup Auto-Hide and it does exactly what it says. By default Firefox (popup) menus disappear when you use the element picker, but you can make them stay around by activating this setting. This makes finding elements and their ids or classes much simpler.

Reference: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox https://developer.mozilla.org/en-US/docs/Tools/Style_Editor

Minimal Firefox userChrome style

Minimal Functional Fox or Minimal Functional Fox (Fork)

Windows Customisation

Adding aliases ala Ubuntu/Linux style

  1. Create a .bat or .cmd file with your DOSKEY commands.

  2. Run (Win+R)regedit and go to HKEY_CURRENT_USER\Software\Microsoft\Command Processor. For Windows 10, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor instead.

  3. Add String Value entry with the name AutoRun and the full path of your .bat or .cmd file.

    For example, %USERPROFILE%\alias.cmd, replacing the initial segment of the path with %USERPROFILE% is useful for syncing among multiple machines.

  4. An example of how to do this:

    1. Create a .bat file and paste this in: doskey np=notepad++.exe $*
    2. Now copy the full path of this file from File Explorer's URL bar, e.g. C:\Users\YourUsername\Documents\MyBatchFile.bat and follow steps 2 and 3.

  5. And you're done! Now if you're in cmd, type in cmd to restart your terminal. Else, if in PowerShell type in . $profile to source your user profile (similar to . .bashrc in Ubuntu) again. This should add your newly created alias(es) to the current and future sessions.

    Credits go to everyone providing detailed answers in Aliases in Windows command prompt.

Adding SSH key to current Git Bash session

  1. Add the following to .profile (store this file in your user folder %USERNAME% or somewhere safe, and add it to PATH for convenience):
env=~/.ssh/agent.env

agent_load_env () { test -f "$env" && . "$env" >| /dev/null ; }

agent_start () {
    (umask 077; ssh-agent >| "$env")
    . "$env" >| /dev/null ; }

agent_load_env

# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= agent not running
agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)

if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
    agent_start
    ssh-add
elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then
    ssh-add
fi

unset env
  1. Running . .profile in Git Bash will request your SSH passphrase, so enter that and you're set for the entire session. This is not a persistent on boot solution.

Credits go to velval on Superuser SE and GitHub article for reference.