Improve placement of explicit IDs for headings
In some cases the IDs of section titles was placed after the section title. With that in the rendered HTML the ID was placed on the paragraph and not on the heading. This led to heading not being shown when the corresponding link was clicked.next
Adaephon-GH
parent
29490c2336
commit
103cef7b2b
|
|
@ -205,9 +205,8 @@ like this:
|
|||
image::tree-layout2.png["layout2",float="right"]
|
||||
image::tree-shot4.png["shot4",title="Two terminals on standard workspace"]
|
||||
|
||||
=== Orientation and Split Containers
|
||||
|
||||
[[OrientationSplit]]
|
||||
=== Orientation and Split Containers
|
||||
|
||||
It is only natural to use so-called +Split Containers+ in order to build a
|
||||
layout when using a tree as data structure. In i3, every +Container+ has an
|
||||
|
|
@ -309,7 +308,6 @@ a # and can only be used at the beginning of a line:
|
|||
-------------------
|
||||
|
||||
[[fonts]]
|
||||
|
||||
=== Fonts
|
||||
|
||||
i3 has support for both X core fonts and FreeType fonts (through Pango) to
|
||||
|
|
@ -342,7 +340,6 @@ font pango:Terminus 11px
|
|||
--------------------------------------------------------------
|
||||
|
||||
[[keybindings]]
|
||||
|
||||
=== Keyboard bindings
|
||||
|
||||
A keyboard binding makes i3 execute a command (see below) upon pressing a
|
||||
|
|
@ -407,7 +404,6 @@ corresponding group. For backwards compatibility, the group “Mode_switch” is
|
|||
alias for Group2.
|
||||
|
||||
[[mousebindings]]
|
||||
|
||||
=== Mouse bindings
|
||||
|
||||
A mouse binding makes i3 execute a command upon pressing a specific mouse
|
||||
|
|
@ -445,7 +441,6 @@ bindsym button8 move right
|
|||
--------------------------------
|
||||
|
||||
[[binding_modes]]
|
||||
|
||||
=== Binding modes
|
||||
|
||||
You can have multiple sets of bindings by using different binding modes. When
|
||||
|
|
@ -498,7 +493,6 @@ mode "$mode_launcher" {
|
|||
------------------------------------------------------------------------
|
||||
|
||||
[[floating_modifier]]
|
||||
|
||||
=== The floating modifier
|
||||
|
||||
To move floating windows with your mouse, you can either grab their titlebar
|
||||
|
|
@ -626,9 +620,8 @@ hide_edge_borders none|vertical|horizontal|both
|
|||
hide_edge_borders vertical
|
||||
----------------------
|
||||
|
||||
=== Arbitrary commands for specific windows (for_window)
|
||||
|
||||
[[for_window]]
|
||||
=== Arbitrary commands for specific windows (for_window)
|
||||
|
||||
With the +for_window+ command, you can let i3 execute any command when it
|
||||
encounters a specific window. This can be used to set windows to floating or to
|
||||
|
|
@ -655,9 +648,8 @@ for_window [title="x200: ~/work"] floating enable
|
|||
|
||||
The valid criteria are the same as those for commands, see <<command_criteria>>.
|
||||
|
||||
=== Don't focus window upon opening
|
||||
|
||||
[[no_focus]]
|
||||
=== Don't focus window upon opening
|
||||
|
||||
When a new window appears, it will be focused. The +no_focus+ directive allows preventing
|
||||
this from happening and must be used in combination with <<command_criteria>>.
|
||||
|
|
@ -681,7 +673,6 @@ no_focus [window_role="pop-up"]
|
|||
-------------------------------
|
||||
|
||||
[[variables]]
|
||||
|
||||
=== Variables
|
||||
|
||||
As you learned in the section about keyboard bindings, you will have
|
||||
|
|
@ -707,9 +698,8 @@ absolutely no plans to change this. If you need a more dynamic configuration
|
|||
you should create a little script which generates a configuration file and run
|
||||
it before starting i3 (for example in your +~/.xsession+ file).
|
||||
|
||||
=== Automatically putting clients on specific workspaces
|
||||
|
||||
[[assign_workspace]]
|
||||
=== Automatically putting clients on specific workspaces
|
||||
|
||||
To automatically make a specific window show up on a specific workspace, you
|
||||
can use an *assignment*. You can match windows by using any criteria,
|
||||
|
|
@ -814,7 +804,6 @@ exec --no-startup-id urxvt
|
|||
The flag --no-startup-id is explained in <<exec>>.
|
||||
|
||||
[[workspace_screen]]
|
||||
|
||||
=== Automatically putting workspaces on specific screens
|
||||
|
||||
If you assign clients to workspaces, it might be handy to put the
|
||||
|
|
@ -1073,9 +1062,8 @@ force_display_urgency_hint <timeout> ms
|
|||
force_display_urgency_hint 500 ms
|
||||
---------------------------------
|
||||
|
||||
=== Focus on window activation
|
||||
|
||||
[[focus_on_window_activation]]
|
||||
=== Focus on window activation
|
||||
|
||||
If a window is activated, e.g., via +google-chrome www.google.com+, it may request
|
||||
to take focus. Since this may not preferable, different reactions can be configured.
|
||||
|
|
@ -1100,6 +1088,7 @@ focus::
|
|||
none::
|
||||
The window will neither be focused, nor be marked urgent.
|
||||
|
||||
[[show_marks]]
|
||||
=== Drawing marks on window decoration
|
||||
|
||||
If activated, marks on windows are drawn in their window decoration. However,
|
||||
|
|
@ -1119,7 +1108,6 @@ show_marks yes
|
|||
--------------
|
||||
|
||||
[[line_continuation]]
|
||||
|
||||
=== Line continuation
|
||||
|
||||
Config files support line continuation, meaning when you end a line in a
|
||||
|
|
@ -1681,7 +1669,6 @@ actually regular expressions (PCRE). See +pcresyntax(3)+ or +perldoc perlre+ for
|
|||
information on how to use them.
|
||||
|
||||
[[exec]]
|
||||
|
||||
=== Executing applications (exec)
|
||||
|
||||
What good is a window manager if you can’t actually start any applications?
|
||||
|
|
@ -1779,7 +1766,6 @@ bindsym $mod+t floating toggle
|
|||
--------------
|
||||
|
||||
[[_focusing_moving_containers]]
|
||||
|
||||
=== Focusing containers
|
||||
|
||||
To change focus, you can use the +focus+ command. The following options are
|
||||
|
|
@ -2015,9 +2001,8 @@ bindsym $mod+r exec i3-input -F 'rename workspace to "%s"' -P 'New name: '
|
|||
See <<move_to_outputs>> for how to move a container/workspace to a different
|
||||
RandR output.
|
||||
|
||||
=== Moving containers/workspaces to RandR outputs
|
||||
|
||||
[[move_to_outputs]]
|
||||
=== Moving containers/workspaces to RandR outputs
|
||||
|
||||
To move a container to another RandR output (addressed by names like +LVDS1+ or
|
||||
+VGA1+) or to a RandR output identified by a specific direction (like +left+,
|
||||
|
|
@ -2060,7 +2045,6 @@ for_window [instance="tabme"] move window to mark target
|
|||
--------------------------------------------------------
|
||||
|
||||
[[resizingconfig]]
|
||||
|
||||
=== Resizing containers/windows
|
||||
|
||||
If you want to resize containers/windows using your keyboard, you can use the
|
||||
|
|
@ -2112,9 +2096,8 @@ with criteria for that.
|
|||
bindsym $mod+a [class="urxvt" title="VIM"] focus
|
||||
------------------------------------------------
|
||||
|
||||
=== VIM-like marks (mark/goto)
|
||||
|
||||
[[vim_like_marks]]
|
||||
=== VIM-like marks (mark/goto)
|
||||
|
||||
This feature is like the jump feature: It allows you to directly jump to a
|
||||
specific window (this means switching to the appropriate workspace and setting
|
||||
|
|
@ -2133,7 +2116,7 @@ The additional +--toggle+ option will remove the mark if the window already has
|
|||
this mark, add it if the window has none or replace the current mark if it has
|
||||
another mark.
|
||||
|
||||
Refer to +show_marks+ if you don't want marks to be shown in the window decoration.
|
||||
Refer to <<show_marks>> if you don't want marks to be shown in the window decoration.
|
||||
|
||||
*Syntax*:
|
||||
------------------------------
|
||||
|
|
@ -2165,7 +2148,6 @@ seperate bindings for a specific set of labels and then only use those labels.
|
|||
///////////////////////////////////////////////////////////////////
|
||||
|
||||
[[pango_markup]]
|
||||
|
||||
=== Window title format
|
||||
|
||||
By default, i3 will simply print the X11 window title. Using +title_format+,
|
||||
|
|
@ -2231,7 +2213,6 @@ bindsym $mod+u border none
|
|||
----------------------------------------------
|
||||
|
||||
[[shmlog]]
|
||||
|
||||
=== Enabling shared memory logging
|
||||
|
||||
As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared
|
||||
|
|
@ -2380,7 +2361,6 @@ bindsym $mod+Shift+b bar mode invisible bar-1
|
|||
------------------------------------------------
|
||||
|
||||
[[multi_monitor]]
|
||||
|
||||
== Multiple monitors
|
||||
|
||||
As you can see in the goal list on the website, i3 was specifically developed
|
||||
|
|
@ -2510,6 +2490,7 @@ position the window either at the top or at the bottom of the screen, depending
|
|||
on which hint the application sets. With i3bar, you can configure its position,
|
||||
see <<i3bar_position>>.
|
||||
|
||||
[[presentations]]
|
||||
=== Giving presentations (multi-monitor)
|
||||
|
||||
When giving a presentation, you typically want the audience to see what you see
|
||||
|
|
@ -2518,7 +2499,6 @@ simple). For more complex presentations, you might want to have some notes
|
|||
which only you can see on your screen, while the audience can only see the
|
||||
slides.
|
||||
|
||||
[[presentations]]
|
||||
==== Case 1: everybody gets the same output
|
||||
This is the simple case. You connect your computer to the video projector,
|
||||
turn on both (computer and video projector) and configure your X server to
|
||||
|
|
|
|||
Loading…
Reference in New Issue