Cynosphere/bug.n
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fixed typos and abbreviations from issue #138

Browse source 
...but without the "key shortcuts"
This commit is contained in:
joten 2018-01-14 22:53:01 +01:00
parent a8e7c8926e
commit e358ef5415
10 changed files with 57 additions and 57 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/Configuring_rules.md
View file

@ -3,7 +3,7 @@
### General description ### General description
Not all windows should be managed by bug.n the same way, or even may not be Not all windows should be managed by bug.n the same way, or even may not be
managable at all. To handle windows differently, you can add rules to the manageable at all. To handle windows differently, you can add rules to the
configuration. configuration.
The general format of a rule added to `Config.ini` is as follows (all in one The general format of a rule added to `Config.ini` is as follows (all in one

4
doc/Default_configuration.md
View file

@ -145,7 +145,7 @@ visible at all, if `Config_barTransparency` is not set to `off`.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
`Config_barCommands=Run, explore doc;Monitor_toggleBar();Reload;ExitApp` `Config_barCommands=Run, explore doc;Monitor_toggleBar();Reload;ExitApp`
The commands seperated by semicolon, which are listed in the command GUI of The commands separated by semicolon, which are listed in the command GUI of
the bar (#!) and therewith can be selected rather then typed; bug.n functions the bar (#!) and therewith can be selected rather then typed; bug.n functions
(as used in the hotkey configuration), the `Run` and `Send` command of (as used in the hotkey configuration), the `Run` and `Send` command of
AutoHotkey can be used here. AutoHotkey can be used here.
@ -364,7 +364,7 @@ list and the stack area.
`Config_onActiveHiddenWnds=view` `Config_onActiveHiddenWnds=view`
The action, which will be taken, if a window e.g. should be activated, but The action, which will be taken, if a window e.g. should be activated, but
is not visible; `view`: show the view accordng to the first tag of the window is not visible; `view`: show the view according to the first tag of the window
in question, `tag`: add the window in question to the current visible view, in question, `tag`: add the window in question to the current visible view,
`hide`: hide the window again ignoring the activation. `hide`: hide the window again ignoring the activation.

4
doc/Installing_and_running.md
View file

@ -18,7 +18,7 @@ There is no installation process for bug.n. Unpack the `zip` file, and you
should be able to run either the executable as it is or the main script should be able to run either the executable as it is or the main script
(`src\Main.ahk`) with [AutoHotkey](http://ahkscript.org/download/). (`src\Main.ahk`) with [AutoHotkey](http://ahkscript.org/download/).
You may copy bug.n anywhere you like -- at least if you have write acces You may copy bug.n anywhere you like -- at least if you have write access
there -- e.g. `C:\Program Files\bugn` or link it to the 'Windows Start Menu' there -- e.g. `C:\Program Files\bugn` or link it to the 'Windows Start Menu'
or the 'Windows Taskbar', for example. or the 'Windows Taskbar', for example.
@ -48,7 +48,7 @@ i. e. _without_ administrator privileges, bug.n will not be able to manage the
associated windows. If you want those application windows to be managed, you associated windows. If you want those application windows to be managed, you
need to run bug.n with administrator privileges, too. need to run bug.n with administrator privileges, too.
You can set the option `Run this program as an administrator` on the You can set the option `Run this program as an administrator` on the
'Compatiblity' tab, section 'Privilege level' of the bug.n executable file 'Compatibility' tab, section 'Privilege level' of the bug.n executable file
properties. But if you also want to run bug.n when Windows starts, you will properties. But if you also want to run bug.n when Windows starts, you will
have to create a task in 'Task Scheduler'. have to create a task in 'Task Scheduler'.

2
doc/Overview.md
View file

@ -14,7 +14,7 @@ hotkeys) for each version of bug.n.
#### [Installing and running bug.n](./Installing_and_running.md) #### [Installing and running bug.n](./Installing_and_running.md)
> A description of how to install and run bug.n. Also described is a method to > A description of how to install and run bug.n. Also described is a method to
run bug.n as Administrator to solve problems with the User Access Control of run bug.n as Administrator to solve problems with the User Access Control of
Microsft Windows higher than Vista. Microsoft Windows higher than Vista.
##### [Stable version](../../../releases/latest) ##### [Stable version](../../../releases/latest)
> The current stable version of bug.n as a package (`.zip` file); it includes > The current stable version of bug.n as a package (`.zip` file); it includes

2
doc/User-hotkeys.md
View file

@ -72,7 +72,7 @@ Here follows an example for configuring hotkeys, which are similar to those of
### AZERTY compatible hotkeys # ### AZERTY compatible hotkeys #
This configuration was created in order to make view/tagging hotkeys functionnal with AZERTY keyboards. In fact, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` and `0` triggers respectively `&`, `é`, `"`, `'`, `(`, `-`, `è`, `_`, `ç` and `à` in such a layout. This configuration was created in order to make view/tagging hotkeys functional with AZERTY keyboards. In fact, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` and `0` triggers respectively `&`, `é`, `"`, `'`, `(`, `-`, `è`, `_`, `ç` and `à` in such a layout.
``` ```
Config_hotkey=#&::Monitor_activateView(1) Config_hotkey=#&::Monitor_activateView(1)