in about:config set:
ui.key.menuAccessKey user set integer 0
ui.key.menuAccessKeyFocuses user set boolean false
how to disable menu bar toggle by ? 19 down vote accepted Actually recently this is the normal behaviour of Firefox. Recently, because few versions earlier it was not like this. And using extensions like Pentadactyl or Vimperator, it is very apparent and annoying, while possibly with the default user interface it's convenient. So I searched for related Firefox settings, and I found, the ui.key.menuAccessKey and ui.key.menuAccessKeyFocuses. First I had the intuition that the first needed to change, which was set to 18, which means the Alt key. I set it to 0, without any effect. Then I changed the latter, from true to false, and the issue become resolved. shareimprove this answer answered Jun 19 '14 at 23:51 deeenes 35629 4 Right now, you need to change ui.key.menuAccessKey. ui.key.menuAccessKeyFocuses will be reset (on start?) if you have the menu bar hidden, so it most likely has no (useful and persistent) effect. This is part of a "bug fix", also introduced to solve what is an accessibility problem for people who use the menu bar interface. Apparently, under GTK, this setting is explicitly set to the boolean negation of the visibility attribute of the menu bar. – njsg Jun 28 '14 at 7:59 1 Thanks for pointing this out, indeed, the ui.key.menuAccessKeyFocuses is reset at restart, and sometimes randomly while running. Now I changed ui.key.menuAccessKey to 0, and surprisingly it works. – deeenes Jul 1 '14 at 10:44 1 @njsg I found out that ui.key.menuAccessKeyFocuses is set to true when you hide menubar with set guioptions-=m. So you have to place set! ui.key.menuAccessKeyFocuses=false after set guioptions-=m in your ~/.pentadactylrc. – Dmitry Alexandrov Jul 24 '14 at 16:45 @njsg What I said in previous comment is enough for FF 30, but not for FF 31 where you indeed need to set ui.key.menuAccessKey=0 – Dmitry Alexandrov Jul 26 '14 at 15:16 I want the menu access key, but it's annoying when I change my mind about using an Alt combination and the menu bar activates. The setting FF could really do with is ui.key.menuAccessKeyTimeout. A timeout is sensible for something like this, so tapping the key will activate the behaviour, but pausing on it and changing your mind will have no effect. Xscape uses a timeout, for example. – pyrocrasty Aug 12 '15 at 21:34 on linux, i needed to set to false : ui.use_unity_menubar, and follow the other instructions from deeenes recommendation. – Josh.F Aug 24 at 5:37
[ ]
@namespace xul url(;

@-moz-document url(chrome://browser/content/browser.xul){
tabbrowser tabpanels { background: #222222 !important} /* prevent white flash; also set "about:blank" to same */
@-moz-document url-prefix(about:blank) {*{background-color:#222222;}}
ADDON: Blank New Tab 1.1.0 автор goodthings Use a blank page as your new tab page. 2016-12-06-16-15-desktop-tar
[ ]
BEFORE YOU EVEN TRY TO CHANGE IT, READ FUCKING THIS: xfce can't change window title window title xfwm4 ignored xfce window title theme
The title bar background colour and font are provided by the Window Manager (xfwm4) theme component. This is set at Settings Manager > Window Manager > Style.
The title bar background colour and font are provided by the Window Manager (xfwm4) theme component. This is set at Settings Manager > Window Manager > Style.
This is set at Settings Manager > Window Manager > Style.
This is set at Settings Manager > Window Manager > Style.
This is set at Settings Manager > Window Manager > Style.
This is set at Settings Manager > Window Manager > Style.
[ ]
how can I add a button to the --question dialog ? in python, tkmessagebox allows it, on windows messagebox also allows it, but I can't find how to do it with zenity.

[+12947] RED TEH FUCKING MANUEL YU FITLHY EINMAL!! http://then-things-you-cant-do-with-zenity.pdf
You can do it with yad.

yad --width 470 --title "I AM THE TITLE" \
    --text "Have you recovered from alcoholism?" \
    --image "gtk-recovery" \
    --button "Cancel:1" --button "No:2" --button "Yes:0"

case $? in
        echo "Just kidding."
        echo "Me neither!"
        echo "Here's your unsung hero badge dude."
        echo "It's time to crush the bones!"

       0      The user has pressed OK button

       1      The user has pressed Cancel button

       70     The dialog has been closed because the timeout has been reached.

       252    The dialog has been closed by pressing Esc or used the window functions  to  close  the

       Exit  codes  for user-specified buttons must be specified in command line. Even exit code mean
       to print result, odd just return exit code.

[ ]
#!/usr/bin/env bash

CHOICE1=$(zenity --list \
    --height=220 \
    --title="List" \
    --text="Options" \
    --radiolist \
    --column="" --column="Option" \
    FALSE "Shutdown" \
    FALSE "Restart" \
    FALSE "Suspend" \
    TRUE "Hibernate")

case $CHOICE1 in
        echo "shutdown..."
        sudo shutdown -h now
        echo "restart..."
        sudo reboot
        echo "suspend..."
        gnome-screensaver-command -l
        echo "hibernate..."
        sudo s2disk
THIS_SCRIPT_DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )                           
[ ]
strace -feprocess $SHELL

starace trace
[ ]
Unquoted, there is no difference -- they're expanded to all the arguments and they're split accordingly.  The difference comes when quoting. `"$@"` expands to properly quoted arguments and `"$*"` makes all arguments into a single argument. Take this for example:

    function print_args_at {
        printf "%s\n" "$@"
    function print_args_star {
        printf "%s\n" "$*"
    print_args_at "one" "two three" "four"
    print_args_star "one" "two three" "four"


    $ ./ 

    two three

    one two three four


Обе опции не нужны. Всё нормально работает только если их выключить. Без них симлинк и создался и удалился.


auditd пишет говно в лог через набор правил ставящихся по man auditctl. Говно выводится командой "ausearch -r" и парсится командой "ausearch -r|aureport -f --summary" где aureport это парсер. Имена файлов, появляющиеся по --summary отсутствуют нахуй в "ausearch -r" и "aureport -f" поэтому --summary к использованию обязателен.

Ну и если старая версия auditd у меня когда-то работала нормально то в новой auditctl -w /home/user/Desktop -p warx нихуя не реагирует на open read и write вызовы, словно их вообще нет.

С учетом фантастически неебической запутанности данного комплекса из программ, вероятность того что данный баг будет когда-либо найден и уж тем более исправлен нулевая, поэтому самое лучшее что можно сделать с auditd это sudo apt remove auditd, а для мониторинга файлов использовать inotifywait который блядь все равно не работает будучи натравлен на encrypted home directory но зато работает по крайней мере на отдельных её кусках.

inotifywait -mr /home/user/.config # Видит READ OPEN MODIFY
inotifywait -mr /home/user/ # Видит конскую залупу (нихуя и ноль десятых)

Перед оскорблением в комментариях учесть огромный промежуток времени, потерянный мною на (пере)изучение всего этого хлама только для того чтобы в итоге выяснить что ничего из этого нормально не работает.

большие задницы