diff --git a/nixos/doc/manual/configuration/x-windows.chapter.md b/nixos/doc/manual/configuration/x-windows.chapter.md index be185cf4c314..bef35f448874 100644 --- a/nixos/doc/manual/configuration/x-windows.chapter.md +++ b/nixos/doc/manual/configuration/x-windows.chapter.md @@ -69,7 +69,7 @@ Wine, you should also set the following: hardware.opengl.driSupport32Bit = true; ``` -## Auto-login {#sec-x11-auto-login .unnumbered} +## Auto-login {#sec-x11-auto-login} The x11 login screen can be skipped entirely, automatically logging you into your window manager and desktop environment when you boot your @@ -96,7 +96,7 @@ services.xserver.displayManager.autoLogin.enable = true; services.xserver.displayManager.autoLogin.user = "alice"; ``` -## Intel Graphics drivers {#sec-x11--graphics-cards-intel .unnumbered} +## Intel Graphics drivers {#sec-x11--graphics-cards-intel} There are two choices for Intel Graphics drivers in X.org: `modesetting` (included in the xorg-server itself) and `intel` (provided by the @@ -136,7 +136,7 @@ services.xserver.deviceSection = '' Note that this will likely downgrade the performance compared to `modesetting` or `intel` with DRI 3 (default). -## Proprietary NVIDIA drivers {#sec-x11-graphics-cards-nvidia .unnumbered} +## Proprietary NVIDIA drivers {#sec-x11-graphics-cards-nvidia} NVIDIA provides a proprietary driver for its graphics cards that has better 3D performance than the X.org drivers. It is not enabled by @@ -158,7 +158,7 @@ services.xserver.videoDrivers = [ "nvidiaLegacy304" ]; You may need to reboot after enabling this driver to prevent a clash with other kernel modules. -## Proprietary AMD drivers {#sec-x11--graphics-cards-amd .unnumbered} +## Proprietary AMD drivers {#sec-x11--graphics-cards-amd} AMD provides a proprietary driver for its graphics cards that is not enabled by default because it's not Free Software, is often broken in @@ -173,7 +173,7 @@ services.xserver.videoDrivers = [ "amdgpu-pro" ]; You will need to reboot after enabling this driver to prevent a clash with other kernel modules. -## Touchpads {#sec-x11-touchpads .unnumbered} +## Touchpads {#sec-x11-touchpads} Support for Synaptics touchpads (found in many laptops such as the Dell Latitude series) can be enabled as follows: @@ -192,7 +192,7 @@ services.xserver.libinput.touchpad.tapping = false; Note: the use of `services.xserver.synaptics` is deprecated since NixOS 17.09. -## GTK/Qt themes {#sec-x11-gtk-and-qt-themes .unnumbered} +## GTK/Qt themes {#sec-x11-gtk-and-qt-themes} GTK themes can be installed either to user profile or system-wide (via `environment.systemPackages`). To make Qt 5 applications look similar to @@ -204,7 +204,7 @@ qt.platformTheme = "gtk2"; qt.style = "gtk2"; ``` -## Custom XKB layouts {#custom-xkb-layouts .unnumbered} +## Custom XKB layouts {#custom-xkb-layouts} It is possible to install custom [ XKB ](https://en.wikipedia.org/wiki/X_keyboard_extension) keyboard layouts diff --git a/nixos/doc/manual/configuration/xfce.chapter.md b/nixos/doc/manual/configuration/xfce.chapter.md index 60771b36fa9c..a80be2b523e2 100644 --- a/nixos/doc/manual/configuration/xfce.chapter.md +++ b/nixos/doc/manual/configuration/xfce.chapter.md @@ -24,7 +24,7 @@ Some Xfce programs are not installed automatically. To install them manually (system wide), put them into your [](#opt-environment.systemPackages) from `pkgs.xfce`. -## Thunar {#sec-xfce-thunar-plugins .unnumbered} +## Thunar {#sec-xfce-thunar-plugins} Thunar (the Xfce file manager) is automatically enabled when Xfce is enabled. To enable Thunar without enabling Xfce, use the configuration @@ -35,7 +35,7 @@ If you'd like to add extra plugins to Thunar, add them to [](#opt-programs.thunar.plugins). You shouldn't just add them to [](#opt-environment.systemPackages). -## Troubleshooting {#sec-xfce-troubleshooting .unnumbered} +## Troubleshooting {#sec-xfce-troubleshooting} Even after enabling udisks2, volume management might not work. Thunar and/or the desktop takes time to show up. Thunar will spit out this kind diff --git a/nixos/doc/manual/development/option-def.section.md b/nixos/doc/manual/development/option-def.section.md index 22cf38873cf0..6a3dc26b99be 100644 --- a/nixos/doc/manual/development/option-def.section.md +++ b/nixos/doc/manual/development/option-def.section.md @@ -12,7 +12,7 @@ config = { However, sometimes you need to wrap an option definition or set of option definitions in a *property* to achieve certain effects: -## Delaying Conditionals {#sec-option-definitions-delaying-conditionals .unnumbered} +## Delaying Conditionals {#sec-option-definitions-delaying-conditionals} If a set of option definitions is conditional on the value of another option, you may need to use `mkIf`. Consider, for instance: @@ -56,7 +56,7 @@ config = { }; ``` -## Setting Priorities {#sec-option-definitions-setting-priorities .unnumbered} +## Setting Priorities {#sec-option-definitions-setting-priorities} A module can override the definitions of an option in other modules by setting an *override priority*. All option definitions that do not have the lowest @@ -72,7 +72,7 @@ This definition causes all other definitions with priorities above 10 to be discarded. The function `mkForce` is equal to `mkOverride 50`, and `mkDefault` is equal to `mkOverride 1000`. -## Ordering Definitions {#sec-option-definitions-ordering .unnumbered} +## Ordering Definitions {#sec-option-definitions-ordering} It is also possible to influence the order in which the definitions for an option are merged by setting an *order priority* with `mkOrder`. The default order priority is 1000. @@ -89,7 +89,7 @@ definitions in the final list value of `hardware.firmware`. Note that this is different from [override priorities](#sec-option-definitions-setting-priorities): setting an order does not affect whether the definition is included or not. -## Merging Configurations {#sec-option-definitions-merging .unnumbered} +## Merging Configurations {#sec-option-definitions-merging} In conjunction with `mkIf`, it is sometimes useful for a module to return multiple sets of option definitions, to be merged together as if