recentpopularlog in

kme : configsettings   31

retext/ at master · retext-project/retext |
hideToolBar (boolean) - whether to hide the toolbars from the UI (default: false)
tabBarAutoHide (boolean) - whether to hide the tabs bar when only one tab is open (default: false)
useFakeVim (boolean) - whether to use the FakeVim editor, if available (default: false)
retext  markdown  linux  vikeybindings  configfile  configsettings  essential  movein  solution 
8 weeks ago by kme
Optional Features - NeoMutt
set imap_authenticators="login"

when working with DavMail
davmail  mutt  imap  mua  email  configsettings  solution 
may 2019 by kme
You can make readline (and bash) much more user friendly by adding a few options to ~/.inputrc : commandline |
set completion-prefix-display-length 2

This one is insanely useful when you have a folder with lots of similarly named files and you are not sure how far the completion has gone when you press TAB. The first part that has been completed will be replaced by "...", and it is simple to see what you need to type to finish the completion.
inputrc  input  readline  bash  cli  configfile  configsettings  example  newbie  movein  essential 
october 2018 by kme
readline - How do I reload .inputrc using a bash script? - Super User |
Use the bind command:
<code class="language-bash">
bind -f ~/.inputrc

See help bind for more information:
-f filename Read key bindings from FILENAME.
keybindings  macros  inputrc  bash  configfile  configsettings  solution 
october 2018 by kme
Remember all your bash history forever |
WATCH OUT! Old-ass versions of Bash (4.1.x on CentOS 6, for example) will truncate your damn history file if you use HISTFILESIZE=-1 or HISTSIZE=-1.
Append the following lines to /etc/bash.bashrc:
<code class="language-bash">HISTTIMEFORMAT='%F %T '
shopt -s histappend # append to history, don't overwrite it
# attempt to save all lines of a multiple-line command in the same history entry
shopt -s cmdhist
# save multi-line commands to the history with embedded newlines
shopt -s lithist</code>

This configures bash to save every command line typed at the interactive shell prompt (HISTFILESIZE) to ~/.bash_history (default), including a timestamp (HISTTIMEFORMAT) and ignoring consecutive duplicate entries (HISTCONTROL). By setting HISTSIZE to the same value as HISTFILESIZE, all saved commands are read back to memory when a new interactive shell starts. The default value for HISTSIZE (500) would load only a fraction of the saved history.

When saving the history at shell exit, history lines are appended to existing ones, instead of replacing them (shopt -s histappend).

By setting HISTIGNORE=?:??, lines consisting of just one or two characters are discarded from the history (e.g. ls commands).
bash  history  tipsandtricks  configsettings  essential  movein  bashrc 
october 2018 by kme
Tilix: VTE Configuration
2. OR use a login shell

Enable the option in your Tilix Profile (under Preferences) to use a login shell, the screenshot below shows the option that needs to be checked.
tilix  terminix  vte  terminal  linux  annoyance  configsettings  workaround  maybesolution 
november 2017 by kme
maintenance - How do I clean up my dconf database? - Ask Ubuntu

This is possible using the dconf reset command, though it's not clear if that's a side-effect of a bug.

For a single key:

dconf reset "/path/to/the/key"

Must not end with a /.

For a whole path:

dconf reset -f "/path/to/the/path/"

Must end with a /.

If you do this while having dconf-editor opened, it will likely crash.
dconf  gsettings  elementary  configsettings  solution 
june 2017 by kme
Manual:$wgUrlProtocols - MediaWiki
To allow links to local files (which may make sense in an intranet context), put this into your LocalSettings.php:

$wgUrlProtocols[] = "file://";
mediawiki  intranet  urlhandler  hyperlink  configsettings  solution 
march 2017 by kme
Editor Preferences Dialog :: WinSCP -
If you want use different editors for different file-types, specify file mask matching file(s) (or file-types) to be associated with the particular editor. The first editor, whose autoselection mask matches name of edited file, will be used. The order of editors is defined on Editors page of Preferences dialog.
winscp  editor  configsettings  solution 
march 2017 by kme
An introduction to the visual features of GNU Screen
# look and feel for the bottom two lines.
caption always "%{+b rk}%H%{gk} |%c %{yk}%d.%m.%Y | %72=Load: %l %{wk}"
hardstatus alwayslastline "%?%{yk}%-Lw%?%{wb}%n*%f %t%?(%u)%?%?%{yk}%+Lw%?"

Kinda like this one better:
hardstatus alwayslastline
hardstatus string "%{.bW}%-w%{.rW}%n %t%{-}%+w %=%{..G} %H %{..Y} %d/%m %C%a "
caption always "%3n %t%? @%u%?%? [%h]%?"
terminal  multiplexor  configsettings  screen  configfile  solution  reference  hardstatus 
march 2016 by kme
PuTTY configuration - Arabesque
Handy 'tput' magic:
for ((color = 0; color <= 255; color++)); do
tput setaf "$color"
printf "test"

I don't even think Ubuntu has *any* 256 color terminal support without:
apt-get install ncurses-term

but maybe I just forget to set 'TERM=xterm-256color' in the parent shell before running 'tmux'. Hrm.
putty  xterm-256color  terminal  configsettings  solution  essential  ubuntu  movein  dammitbrain 
may 2015 by kme
How to disable images in Firefox?
firefox 29+ version:

enter about:config into the address bar, search for the preference named permissions.default.image, edit it and change its value to 2
firefox  configsettings  webdevel  solution 
july 2014 by kme
Squeezenetwork - Logitech Forums
I believe both the "server_address" and "squeezecenter_address" need to be set to "".

At least that's what I do in iPeng when I send an unconnected player to MySB.

For the local server the combination should be "" for server_address and the server's IP address for squeezecenter_address.
squeezebox  networking  audiovideo  maybesolution  configsettings 
october 2013 by kme
SSH connection stability | The STAR experiment
Solution to dropped SSH connections using TCPKeepAlive and/or ServerAliveInterval:
<code class="language-bash">ssh -o TCPKeepAlive=no -o ServerAliveInterval=15</code>

Full context:

- Your SSH connections are closed from home
- You get disconnected from any nodes without any reasons?
- ... and you are a PuTTY user
- ... or an Uglix SSH client user

This page is for you. If you are another user, use different clients and so on, this page may still be informative and help you stabalize your connection (the same principles apply).

PuTTY users

PuTTY to connect to gateway (from a home connection), you have to

- set a session, be sure to enable SSH
- go to the 'Connection' menu and have the following options box checked
- Disable Nagle's algorithm (TCP_NODELAY option)
- Enable TCP keepalives (SO_KEEPALIVE option)
- Furthermore, in 'Connection' -> 'SSH' -> 'Tunnels' enable the option
- Enable X11 forwarding
- Enable MIT-Magic-Cookie-1
- Save the session

Documentation on those features (explanation for the interested) are added at the end of this document.

SSH Users

SSH users and owner of their system could first of all be sure to manipulate the SSH client configuration file and be sure settings are turned on by default. The client configuration is likely located as /etc/ssh_config or /usr/local/etc/ssh_config depending on where you have ssh installed.

But if you do NOT have access to the configuration file, the client can nonetheless pass on options from the command line. Those options would have the same name as they would appear in the config file.

Especially, KEEP_ALIVE is controlled via the SSH configuration option TCPKeepAlive.

% ssh -o TCPKeepAlive=yes

You will note in the next section that a spoofing issue exists with keep alive (I know it works well, but please consider the ServerAliveCountMax mechanism) so, you may use instead

% ssh -o TCPKeepAlive=no -o ServerAliveInterval=15

Note that the value 15 in our example is purely empirical. There are NO magic values and you need to test your connection and detect when (after what time) you get kicked out and disconnected and set the parameters from your client accordingly. Let's explain the default first and come back to this and a rule of thumb.

There are two relevant parameters (in addition of TCPKeepAlive):


Sets a timeout interval in seconds after which if no data has been received from the server, ssh will send a message through the encrypted channel to request a response from the server. The default is 0, indicating that these messages will not be sent to the server.

This option applies to protocol version 2 only.


Sets the number of server alive messages (see above) which may be sent without ssh receiving any messages back from the server. If this threshold is reached while server alive messages are being sent, ssh will disconnect from the server, terminating the session. It is important to note that the use of server alive messages is very different from TCPKeepAlive (below). The server alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The server alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

The default value is 3. If, for example, ServerAliveInterval (above) is set to 15, and ServerAliveCountMax is left at the default, if the server becomes unresponsive ssh will disconnect after approximately 45 seconds.

In our example

% ssh -o TCPKeepAlive=no -o ServerAliveInterval=15

The recipe should be: if you get disconnected after N seconds, play with the above and be sure to set a

time of ServerAliveInterval*ServerAliveCountMax <= 0.8*N, N being the timeout. Since ServerAliveCountMax is typically not modified, in our example we assume the default value of 3 and therefore a a 3x15 = 45 seconds (and we guessed a disconnect every minute or so). If you set the value too low, the client will send to much "chatting" to the server and there will be a traffic impact.

Nagle's algorithm

This was written based on this article.

RPC implementations on TCP should disable Nagle. This reduces average RPC request latency on TCP, and makes network trace tools work a little nicer.

Determines whether Nagle's algorithm is to be used. The Nagle's algorithm tries to conserve bandwidth by minimizing the number of segments that are sent. When applications wish to decrease network latency and increase performance, they can disable Nagle's algorithm (that is enable TCP_NODELAY). Data will be sent earlier, at the cost of an increase in bandwidth consumption.


The KEEPALIVE option of the TCP/IP Protocol ensures that connections are kept alive even while they are idle. When a connection to a client is inactive for a period of time (the timeout period), the operating system sends KEEPALIVE packets at regular intervals. On most systems, the default timeout period is two hours (7,200,000 ms).

If the network hardware or software drops connections that have been idle for less than the two hour default, the Windows Client session will fail. KEEPALIVE timeouts are configured at the operating system level for all connections that have KEEPALIVE enabled.

If the network hardware or software (including firewalls) have a idle limit of one hour, then the KEEPALIVE timeout must be less than one hour. To rectify this situation TCP/IP KEEPALIVE settings can be lowered to fit inside the firewall limits. The implementation of TCP KEEPALIVE may vary from vendor to vendor. The original definition is quite old and described in RFC 1122.

MIT Magic cookie

To avoid unauthorized connections to your X display, the command xauth for encrypted X connections is widely used. When you login, a .Xauthority file is created in your home directory ($HOME). Even SSH initiate the creation of a magic cookie and without it, no display could be opened. Note that since the .Xauthority file IS the file containing the MIT Magic cookie, if you ever run out of disk quota or the file system is full, this file CANNOT be created or updated (even from the sshd impersonating the user) and consequently, no X connections can be opened.

The .Xauthority file sometimes contains information from older sessions, but this is not important, as a new key is created at every login session. The Xauthority is simple and powerful, and eliminates many of the security problems with X.
ssh  configsettings  putty  RemoteAdministration  solution  tipsandtricks  tricks  annoyance  essential  movein 
august 2010 by kme

Copy this bookmark:

to read