https://wiki.archlinux.org/api.php?action=feedcontributions&user=Sistematico&feedformat=atomArchWiki - User contributions [en]2024-03-29T12:05:48ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Xfce&diff=580353Xfce2019-08-18T20:26:40Z<p>Sistematico: Added Português to Languages</p>
<hr />
<div>[[Category:Xfce]]<br />
[[cs:Xfce]]<br />
[[de:Xfce]]<br />
[[es:Xfce]]<br />
[[fa:Xfce]]<br />
[[fr:Xfce]]<br />
[[it:Xfce]]<br />
[[ja:Xfce]]<br />
[[ko:Xfce]]<br />
[[pl:Xfce]]<br />
[[pt:Xfce]]<br />
[[ru:Xfce]]<br />
[[zh-hans:Xfce]]<br />
{{Related articles start}}<br />
{{Related|Desktop environment}}<br />
{{Related|Window manager}}<br />
{{Related|Xfwm}}<br />
{{Related|Thunar}}<br />
{{Related|LXDE}}<br />
{{Related|GNOME}}<br />
{{Related articles end}}<br />
<br />
[http://www.xfce.org Xfce] is a lightweight and modular [[desktop environment]] currently based on both GTK 2 and GTK 3. To provide a complete user experience, it includes a window manager, a file manager, desktop and panel.<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Grp|xfce4}} group. You may also wish to install the {{Grp|xfce4-goodies}} group which includes extra plugins and a number of useful utilities such as the {{Pkg|mousepad}} editor. Xfce uses the [[Xfwm]] window manager by default.<br />
<br />
== Starting ==<br />
<br />
Choose ''Xfce Session'' from the menu in a [[display manager]] of choice, or add {{ic|exec startxfce4}} to [[Xinitrc]].<br />
<br />
{{Note|Do not call the {{ic|xfce4-session}} executable directly; {{ic|startxfce4}} is the correct command which, in turn, calls the former when appropriate.}}<br />
<br />
== Configuration ==<br />
<br />
Xfce stores configuration options in [http://docs.xfce.org/xfce/xfconf/start Xfconf]. There are several ways to modify these options:<br />
<br />
* In the main menu, select [http://docs.xfce.org/xfce/xfce4-settings/start Settings] and the category you want to customize. Categories are programs usually located in {{ic|/usr/bin/xfce4-*}} and {{ic|/usr/bin/xfdesktop-settings}}.<br />
* {{ic|xfce4-settings-editor}} can see and modify all settings. Options modified here will take effect immediately. Use {{ic|xfconf-query}} to change settings from the commandline; see [http://docs.xfce.org/xfce/xfconf/xfconf-query the documentation] for details.<br />
* Settings are stored in XML files in {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/}} which can be edited by hand. However, changes made here will ''not'' take effect immediately.<br />
<br />
=== Menu ===<br />
<br />
See [[Xdg-menu]] for more info on using the Free Desktop menu system.<br />
<br />
==== Whisker menu ====<br />
<br />
{{Pkg|xfce4-whiskermenu-plugin}} (also part of {{Grp|xfce4-goodies}}) is an alternative application launcher. It shows a list of favorites, browses through all installed applications through category buttons, and supports fuzzy searching. After package being installed, it can replace ''Applications Menu'' as first item in Panel 1 (in ''Settings > Panel > Items'' add ''Whisker Menu'').<br />
<br />
==== Edit entries ====<br />
<br />
A number of graphical tools are available for this task:<br />
<br />
* {{App|MenuLibre|An advanced menu editor that provides modern features in a clean, easy-to-use interface.|https://launchpad.net/menulibre|{{AUR|menulibre}}}}.<br />
* {{App|Alacarte|Menu editor for GNOME|http://www.gnome.org/|{{Pkg|alacarte}}}}<br />
* {{App|XAME (XFCE Applications Menu Editor)|GUI tool written in Gambas designed specifically for editing menu entries in Xfce, it will not work in other environments. (Discontinued)|http://redsquirrel87.altervista.org/doku.php/xfce-applications-menu-editor|{{AUR|xame}}}}<br />
<br />
Alternatively, create the file {{ic|~/.config/menus/xfce-applications.menu}} manually. See the example configuration below:<br />
<br />
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"<br />
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd"><br />
<br />
<Menu><br />
<Name>Xfce</Name><br />
<MergeFile type="parent">/etc/xdg/menus/xfce-applications.menu</MergeFile><br />
<br />
<Exclude><br />
<Filename>xfce4-run.desktop</Filename><br />
<Filename>exo-terminal-emulator.desktop</Filename><br />
<Filename>exo-file-manager.desktop</Filename><br />
<Filename>exo-mail-reader.desktop</Filename><br />
<Filename>exo-web-browser.desktop</Filename><br />
<Filename>xfce4-about.desktop</Filename><br />
<Filename>xfhelp4.desktop</Filename><br />
</Exclude><br />
<br />
<Layout><br />
<Merge type="all"/><br />
<Separator/><br />
<Menuname>Settings</Menuname><br />
<Separator/><br />
<Filename>xfce4-session-logout.desktop</Filename><br />
</Layout><br />
</Menu><br />
<br />
The {{ic|<MergeFile>}} tag includes the default Xfce menu.<br />
<br />
The {{ic|<Exclude>}} tag excludes applications which we do not want to appear in the menu. Here we excluded some Xfce default shortcuts, but you can exclude {{ic|firefox.desktop}} or any other application.<br />
<br />
The {{ic|<Layout>}} tag defines the layout of the menu. The applications can be organized in folders or however we wish. For more details see the [http://wiki.xfce.org/howto/customize-menu Xfce wiki].<br />
<br />
You can also make changes to the Xfce menu by editing the {{ic|.desktop}} files themselves. To hide entries, see [[Desktop entries#Hide desktop entries]]. You can edit the application's category by modifying the {{ic|1=Categories=}} line of the desktop entry, see [[Desktop entries#File example]].<br />
<br />
=== Desktop ===<br />
<br />
==== Transparent background for icon titles ====<br />
<br />
To change the default white background of desktop icon titles to something more suitable, create or edit {{ic|~/.gtkrc-2.0}}:<br />
<br />
{{bc|<nowiki><br />
style "xfdesktop-icon-view" {<br />
XfdesktopIconView::label-alpha = 10<br />
base[NORMAL] = "#000000"<br />
base[SELECTED] = "#71B9FF"<br />
base[ACTIVE] = "#71B9FF"<br />
fg[NORMAL] = "#fcfcfc"<br />
fg[SELECTED] = "#ffffff"<br />
fg[ACTIVE] = "#ffffff"<br />
}<br />
widget_class "*XfdesktopIconView*" style "xfdesktop-icon-view"<br />
</nowiki>}}<br />
<br />
==== Remove desktop icons ====<br />
<br />
Issue the following command:<br />
<br />
$ xfconf-query -c xfce4-desktop -v --create -p /desktop-icons/style -t int -s 0<br />
<br />
To reinstate icons on the desktop, issue the same command with a value of 2.<br />
<br />
==== One wallpaper across multihead ====<br />
<br />
Open {{ic|xfce4-settings-editor}} and create a new property with the following settings:<br />
<br />
Property: /backdrop/screen0/xinerama-stretch<br />
Type: Boolean<br />
Value: TRUE|1|Enabled<br />
<br />
==== Kill window shortcut ====<br />
<br />
Xfce does not have a shortcut to kill a window, for example when a program freezes.<br />
<br />
With {{Pkg|xorg-xkill}}, use {{ic|xkill}} to interactively kill a window. For the currently active window, use {{Pkg|xdotool}}:<br />
<br />
$ xdotool getwindowfocus windowkill<br />
<br />
Alternatively:<br />
<br />
$ sh -c "xkill -id $(xprop -root -notype | sed -n '/^_NET_ACTIVE_WINDOW/ s/^.*# *\|\,.*$//g p')"<br />
<br />
To add the shortcut, use ''Settings > Keyboard'' or an application like {{pkg|xbindkeys}}.<br />
<br />
=== Session ===<br />
<br />
==== Autostart ====<br />
<br />
To launch custom applications when Xfce starts up, click the ''Applications Menu > Settings > Settings Manager'' and then choose the ''Session and Startup'' option and click the tab ''Application Autostart''.<br />
You will see a list of programs that get launched on startup. To add an entry, click the ''Add'' button and fill out the form, specifying the path to an executable you want to run.<br />
<br />
Autostart applications are stored as {{ic|''name''.desktop}} in {{ic|~/.config/autostart/}}.<br />
<br />
Alternatively, add the commands you wish to run (including setting environment variables) to [[xinitrc]] (or [[xprofile]] when a [[display manager]] is being used).<br />
<br />
{{Tip|Sometimes it might be useful to '''delay the startup of an application'''. Note that specifying under ''Application > Autostart'' a command such as {{ic|sleep 3 && ''command''}} does not work; a workaround is to use the syntax {{ic|sh -c "sleep 3 && ''command''"}}<br />
}}<br />
<br />
==== Lock the screen ====<br />
''xflock4'' is the reference Bash script which is used to lock an Xfce session.<br />
<br />
It tries to lock the screen with either {{Pkg|xscreensaver}}, {{Pkg|gnome-screensaver}}, {{Pkg|slock}} or {{Pkg|xlockmore}}. It consecutively looks for the corresponding binary or exits with return code 1 if it fails to find any of these four. <br />
<br />
The [[List of applications/Security#Screen lockers]] contains a short description of these four screen lockers together with other popular applications. There is in this list an alternative locker, {{Pkg|light-locker}}, which integrates particularly well with {{Pkg|xfce4-power-manager}}. Once it is installed, Xfce Power Manager's setting gains an additional ''Security'' tab to configure ''light-locker'' and the existing ''Lock screen when system is going for sleep'' setting is relocated under this tab. In this new GUI it is possible to set whether the session should be locked upon screensaver activity or whenever the system goes to sleep.<br />
<br />
To have ''xflock4'' run ''light-locker'' or any custom session locker, not among the four cited above, one must set {{ic|LockCommand}} in the session's xfconf channel to the command line to be used (the command inside the quotes in the following example can be adapted accordingly for other screen lockers):<br />
<br />
{{bc|$ xfconf-query -c xfce4-session -p /general/LockCommand -s "''light-locker-command --lock''" --create -t string}}<br />
<br />
The panel lock button in the ''Action Buttons'' panel simply executes {{ic|/usr/bin/xflock4}}. It should work as expected as long as ''xflock4'' is functioning i.e. one of the native lockers is installed or a custom locker is configured to integrate with it as proposed above.<br />
<br />
==== Suspend ====<br />
Whenever asked to suspend, Xfce executes the {{man|1|xfce4-session-logout}} command with the {{ic|suspend}} option:<br />
<br />
$ xfce4-session-logout --suspend<br />
<br />
Whether or not the session is systematically locked on ''suspend'' can be configured through the xfconf properties or from the GUI.<br />
<br />
To control this state using the CLI: there are two settings that are used, {{ic|LockScreen}} and {{ic|lock-screen-suspend-hibernate}}, in respectively the session and the power manager xfconf channels.<br />
To prevent locking on suspend, turn them to {{ic|false}}:<br />
$ xfconf-query -c xfce4-session -p /shutdown/LockScreen -s '''false'''<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/lock-screen-suspend-hibernate -s '''false'''<br />
Similarly, turn them to {{ic|true}} to lock the session on suspend.<br />
<br />
The setting can also be controlled from the GUI: open the ''Session and Startup'' application and turn the flag ''Advanced > Lock screen before sleep'' on or off.<br />
<br />
Whenever the suspend keyboard button is pressed, it can be handled by either Xfce's power manager or by ''systemd-logind''. To give precedence to logind, the following xfconf setting must be set to {{ic|true}}:<br />
<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-suspend-key -n -t bool -s '''true'''<br />
<br />
{{Note|To check how ''systemd-logind'' handles events whenever it has precedence over Xfce, check {{man|5|logind.conf}}}}<br />
<br />
==== Disable saved sessions ====<br />
<br />
Per user, saved sessions can be disabled by executing the following:<br />
$ xfconf-query -c xfce4-session -p /general/SaveOnExit -s false<br />
Then navigate to ''Applications > Settings > Session and Startup > Sessions'' and press the ''Clear saved sessions'' button to remove all previously saved sessions.<br />
<br />
{{Tip|If the command above does not change the setting persistently, use the following command instead: {{ic|xfconf-query -c xfce4-session -p /general/SaveOnExit -n -t bool -s false}}}}<br />
<br />
Alternatively, Xfce [https://wiki.xfce.org/howto/kiosk_mode kiosk mode] can be used to disable the saving of sessions systemwide. To disable sessions, create or edit the file {{ic|/etc/xdg/xfce4/kiosk/kioskrc}} and add the following:<br />
<br />
[xfce4-session]<br />
SaveSession=NONE<br />
<br />
If kiosk mode is not working, the user can set read only permissions for the sessions directory:<br />
<br />
$ rm ~/.cache/sessions/* && chmod 500 ~/.cache/sessions<br />
<br />
This will prevent Xfce from saving any sessions despite any configuration that specifies otherwise.<br />
<br />
==== Use a different window manager ====<br />
<br />
{{Note|For the changes to take effect, you will need to clear the saved sessions and ensure that session saving is disabled when logging out for the first time. Once the window manager of choice is running, session saving can be enabled again.}}<br />
<br />
The files specifying the default window manager are found in the following locations:<br />
*{{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}} - per user<br />
*{{ic|/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}} - systemwide<br />
<br />
The default window manager for the user can be set easily using ''xfconf-query'':<br />
$ xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -sa ''wm_name''<br />
<br />
If you want to start the window manager with command line options, see the command below:<br />
$ xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -t string -s ''wm_name'' -s ''--wm-option''<br />
If you need more command line options, simply add more {{ic|-t string}} and {{ic|-s ''--wm-option''}} arguments to the command.<br />
<br />
If you want to change the default window manager systemwide, edit the file specified above manually, changing ''xfwm4'' to the preferred window manager and adding more {{ic|1=<value type="string" value="''--wm-option''"/>}} lines for extra command line options if needed.<br />
<br />
You can also change the window manager by autostarting {{ic|''wm_name'' --replace}} using the autostart facility or by running {{ic|''wm_name'' --replace &}} in a terminal and making sure the session is saved on logout. Be aware though that this method does not truly change the default manager, it merely replaces it at login. Note that if you are using the autostart facility, you should disable saved sessions as this could lead to the new window manager being started twice after the default window manager.<br />
<br />
=== Theming ===<br />
<br />
XFCE themes are available at [http://www.xfce-look.org xfce-look.org]. ''Xfwm'' themes are stored in {{ic|/usr/share/themes/xfce4}}, and set in ''Settings > Window Manager''. [[GTK]] themes are set in ''Settings > Appearance''.<br />
<br />
To achieve a uniform look for all applications, see [[Uniform look for Qt and GTK applications]].<br />
<br />
See also [[Cursor themes]], [[Icons]], and [[Font configuration]].<br />
<br />
=== Sound ===<br />
<br />
==== Sound themes ====<br />
<br />
XFCE4 supports [https://www.freedesktop.org/wiki/Specifications/sound-theme-spec/ freedesktop system sounds], but it is not configured out of the box.<br />
<br />
To enable a sound theme:<br />
<br />
# Install {{Pkg|libcanberra}} and {{Pkg|libcanberra-pulse}} for [[PulseAudio]] support;<br />
# "canberra-gtk-module" should be in the GTK_MODULES environment variable (re-login may be required);<br />
# Check "Enable event sounds" in Settings Manager → Appearance → Settings tab;<br />
# In the Settings Editor set "xsettings/Net/SoundThemeName" to a sound theme located in {{Ic|/usr/share/sounds/}};<br />
# Turn on "System Sounds" in audio mixer (e.g. pavucontrol).<br />
<br />
{{Pkg|sound-theme-freedesktop}} provides a compatible sound theme, but it lacks many required events. A better choice is {{AUR|sound-theme-smooth}} (SoundThemeName should be "Smooth").<br />
<br />
==== Keyboard volume buttons ====<br />
<br />
{{Pkg|xfce4-pulseaudio-plugin}} provides a panel applet which has support for keyboard volume control and volume notifications. As an alternative, you can install {{AUR|xfce4-volumed-pulse}}, which also provides keybinding and notification control, but without an icon sitting in the panel. This is handy, for example, when using {{Pkg|pasystray}} at the same time for a finer control.<br />
<br />
Alternatively, {{AUR|xfce4-mixer}} also provides a panel applet and keyboard shortcuts which supports Alsa as well. Note however, that it is based on a feature of GStreamer 0.10 which has been abandoned in 1.0.<br />
<br />
For non desktop environment specific alternatives, see [[List of applications/Multimedia#Volume control]].<br />
<br />
===== Shortcuts =====<br />
<br />
If you are not using an applet or daemon that controls the volume keys, you can map volume control commands to your volume keys manually using Xfce's keyboard settings. For the sound system you are using, see the sections linked to below for the appropriate commands.<br />
*ALSA: see [[Advanced Linux Sound Architecture#Keyboard volume control]].<br />
*PulseAudio: see [[PulseAudio#Keyboard volume control]]<br />
*OSS: see [[OSS#Using multimedia keys with OSS]].<br />
<br />
=== Keyboard Shortcuts ===<br />
<br />
Keyboard shortcuts are defined in two places: ''Settings > Window Manager > Keyboard'', and ''Settings > Keyboard > Shortcuts''.<br />
<br />
=== Polkit Authentication Agent ===<br />
<br />
The {{Pkg|polkit-gnome}} agent will be installed along with {{Pkg|xfce4-session}} and autostarted automatically; no user intervention is required. For more information, see [[Polkit#Authentication agents]].<br />
<br />
A third party polkit authentication agent for Xfce is also available, see {{AUR|xfce-polkit}} or {{AUR|xfce-polkit-git}}.<br />
<br />
=== Display blanking ===<br />
Some programs that are commonly used with Xfce will control monitor blanking and [[DPMS]] (monitor powersaving) settings. They are discussed below.<br />
<br />
;Xfce Power Manager<br />
''Xfce Power Manager'' controls blanking and DPMS settings. These settings can be configured in the ''Power Manager'' GUI within the ''Display'' tab.<br />
<br />
Note that when ''Display power management'' is turned off, DPMS is fully disabled, it does not mean that ''Power Manager'' will simply stop controlling DPMS. It does not disable screen blanking either. To disable both blanking and DPMS, right click on the power manager system tray icon or left click on the panel applet and make sure that the option labelled ''Presentation mode'' is ticked.<br />
<br />
;XScreenSaver<br />
If {{pkg|xscreensaver}} is installed and runs alongside Xfce Power Manager, it may not be clear which application is in control of blanking and DPMS as both are competing for control of the same settings. Therefore, in a situation where it is important that the monitor not be blanked (when watching a video for instance), it is advisable to disable blanking and DPMS through both applications. To know more about ''XScreenSaver'' options, see [[XScreenSaver#DPMS and blanking settings]].<br />
<br />
;xset<br />
If neither of the above applications are running, then blanking and DPMS settings can be controlled using the ''xset'' command, see [[DPMS#Modify DPMS and screensaver settings with a command]].<br />
<br />
{{Note|1=There are some issues associated with blanking and resuming from blanking in some configurations. See [https://bbs.archlinux.org/viewtopic.php?id=194313&p=2][https://bugzilla.xfce.org/show_bug.cgi?id=11107].}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Hide partitions from thunar and xfdesktop ===<br />
<br />
If your installation partitions are shown as mounted devices on the desktop and in Thunar, try to install {{Pkg|gvfs}}. See [[Udisks#Hide selected partitions]] for more advanced configuration options.<br />
<br />
=== Screenshots ===<br />
<br />
Xfce has its own screenshot tool, {{pkg|xfce4-screenshooter}}. It is part of the {{grp|xfce4-goodies}} group.<br />
<br />
Go to ''Applications > Settings > Keyboard'', ''Application Shortcuts''. Add the {{ic|xfce4-screenshooter -f}} (or {{ic|-w}} for the active window) command to use the {{ic|Print}} key in order to take fullscreen screenshots. See screenshooter's man page for other optional arguments.<br />
<br />
Alternatively, an independent screenshot program like [[Taking a screenshot#scrot|scrot]] can be used.<br />
<br />
=== Disable Terminal F1 and F11 shortcuts ===<br />
<br />
The xfce terminal binds F1 and F11 to help and fullscreen, respectively, which can make using programs like htop difficult. To disable those shortcuts, create or edit its configuration file, then log out and log back in. F10 can disabled in the Preferences menu.<br />
<br />
{{hc|~/.config/xfce4/terminal/accels.scm|<br />
(gtk_accel_path "<Actions>/terminal-window/fullscreen" "")<br />
(gtk_accel_path "<Actions>/terminal-window/contents" "")<br />
}}<br />
<br />
=== Terminal color themes or palettes ===<br />
<br />
Terminal color themes or palettes can be changed in GUI under Appearance tab in Preferences. These are the colors that are available to most console applications like [[Emacs]], [[Vi]] and so on. Their settings are stored individually for each system user in {{ic|~/.config/xfce4/terminal/terminalrc}} file. There are also so many other themes to choose from. Check forum thread [https://bbs.archlinux.org/viewtopic.php?id=51818 Terminal Colour Scheme Screenshots] for hundreds of available choices and themes.<br />
<br />
==== Changing default color theme ====<br />
<br />
Xfce's {{ic|extra/terminal}} package comes with a darker colour palette. To change this, append the following in your terminalrc file for a lighter color theme, that is always visible in darker Terminal backgrounds.<br />
<br />
{{hc|~/.config/xfce4/terminal/terminalrc|2=<br />
ColorPalette5=#38d0fcaaf3a9<br />
ColorPalette4=#e013a0a1612f<br />
ColorPalette2=#d456a81b7b42<br />
ColorPalette6=#ffff7062ffff<br />
ColorPalette3=#7ffff7bd7fff<br />
ColorPalette13=#82108210ffff}}<br />
<br />
==== Terminal tango color theme ====<br />
<br />
To switch to tango color theme, open with your favorite editor<br />
<br />
~/.config/xfce4/terminal/terminalrc<br />
<br />
And add(replace) these lines:<br />
<br />
ColorForeground=White<br />
ColorBackground=#323232323232<br />
ColorPalette1=#2e2e34343636<br />
ColorPalette2=#cccc00000000<br />
ColorPalette3=#4e4e9a9a0606<br />
ColorPalette4=#c4c4a0a00000<br />
ColorPalette5=#34346565a4a4<br />
ColorPalette6=#757550507b7b<br />
ColorPalette7=#060698989a9a<br />
ColorPalette8=#d3d3d7d7cfcf<br />
ColorPalette9=#555557575353<br />
ColorPalette10=#efef29292929<br />
ColorPalette11=#8a8ae2e23434<br />
ColorPalette12=#fcfce9e94f4f<br />
ColorPalette13=#72729f9fcfcf<br />
ColorPalette14=#adad7f7fa8a8<br />
ColorPalette15=#3434e2e2e2e2<br />
ColorPalette16=#eeeeeeeeecec<br />
<br />
=== Open URLs by middle mouse in terminal ===<br />
On update to version 0.8 open URL with middle mouse turned off by default and just paste clip to cursor.<br />
To enable old behavior fix next option in {{ic|${XDG_CONFIG_HOME}/xfce4/terminal/terminalrc}} ({{ic|<nowiki>XDG_CONFIG_HOME=${HOME}/.config</nowiki>}} by default)<br />
{{hc|${XDG_CONFIG_HOME}/xfce4/terminal/terminalrc|<nowiki>[Configuration]<br />
MiscMiddleClickOpensUri=TRUE</nowiki>}}<br />
<br />
=== Colour management ===<br />
<br />
Xfce has no native support for colour management. [https://bugzilla.xfce.org/show_bug.cgi?id=8559] See [[ICC profiles]] for alternatives.<br />
<br />
=== Multiple monitors ===<br />
<br />
Xfce has support for multiple monitors. Settings can be configured in the ''Applications > Settings > Display'' dialog. For more information, see the [http://docs.xfce.org/xfce/xfce4-settings/display display] article from the Xfce documentation.<br />
<br />
XFCE's display configuration is not persistent so you may find yourself needing to use the display tool a lot, especially if you use multiple displays. One workaround for this is to use {{pkg|arandr}} to easily configure your display configurations in the form of xrandr commands which you can assign to be executed as XFCE keyboard shortcuts.<br />
<br />
=== SSH agents ===<br />
<br />
By default Xfce 4.10 will try to load gpg-agent or ssh-agent in that order during session initialization. To disable this, create an xfconf key using the following command:<br />
<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
To force using ssh-agent even if gpg-agent is installed, run the following instead:<br />
<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/type -n -t string -s ssh-agent<br />
<br />
To use [[GNOME Keyring]], simply tick the checkbox ''Launch GNOME services on startup'' in the ''Advanced'' tab of ''Session and Startup'' in Xfce's settings. This will also disable gpg-agent and ssh-agent.<br />
<br />
Source: http://docs.xfce.org/xfce/xfce4-session/advanced<br />
<br />
=== Scroll a background window without shifting focus on it ===<br />
<br />
Go to ''Main Menu > Settings > Window Manager Tweaks > Accessibility'' tab.<br />
Uncheck ''Raise windows when any mouse button is pressed''.<br />
<br />
=== Mouse button modifier ===<br />
<br />
By default, the mouse button modifier in Xfce is set to {{ic|Alt}}. This can be changed with ''xfconf-query''. For instance, the following command will set the {{ic|Super}} key as the mouse button modifier:<br />
<br />
$ xfconf-query -c xfwm4 -p /general/easy_click -n -t string -s "Super"<br />
<br />
Strictly speaking, using multiple modifiers is not supported. However, as a workaround, multiple modifiers can be specified if the key names are separated with {{ic|><}}. For instance, to set {{ic|Ctrl+Alt}} as the mouse button modifier, you can use the following command:<br />
<br />
$ xfconf-query -c xfwm4 -p /general/easy_click -n -t string -s "Ctrl><Alt"<br />
<br />
=== Set the two fingers click to middle click for a touchpad ===<br />
<br />
{{Style|Convoluted way of simply configuring [[Touchpad Synaptics]]}}<br />
<br />
If you want the 2 finger click on the touchpad to do a middle click, create or edit the following file:<br />
<br />
{{hc|~/.config/xfce4/xfconf/xfce-perchannel-xml/pointers.xml|<nowiki><br />
<channel name="pointers" version="1.0"><br />
<property name="SynPS2_Synaptics_TouchPad" type="empty"><br />
<property name="Properties" type="empty"><br />
<property name="Synaptics_Tap_Action" type="array"><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="1"/><br />
<value type="int" value="2"/><br />
<value type="int" value="3"/><br />
</property><br />
</property><br />
</property><br />
</channel><br />
</nowiki>}}<br />
<br />
The 2 in the array is the middle click.<br />
<br />
=== Limit the minimum brightness of the brightness-slider ===<br />
Limiting the minimum brightness can be useful for displays which turn off backlight on a brightness level of 0. In {{ic|xfce4-power-manager 1.3.2}} a new hidden option had been introduced to set a minimum brightness value with a xfconf4-property. Add {{ic|brightness-slider-min-level}} as an int property in xfconf4. Adjust the int value to get a suitable minimum brightness level.<br />
<br />
=== Adding profile pictures ===<br />
To add profile pictures for each user to be displayed in the whisker-menu, simply place a 96x96 PNG file in the respective user's home directory with the name {{ic|.face}}. For example the PNG file {{ic|/home/''bob''/.face}} for user ''bob''.<br />
<br />
Image editing programs like [[GIMP]] can be used to convert and scale your favourite images down to 96x96.<br />
<br />
=== Power manager plugin label ===<br />
<br />
The xfconf option {{ic|show-panel-label}} of type {{ic|int}} controls the label of the power manager, it can be configured for different label formats: it can be set to 0 (no label), 1 (percentage), 2 (remaining time) or 3 (both).<br />
<br />
It is also accessible through the power manager plugin GUI in ''Properties > Show label''<br />
<br />
== Troubleshooting ==<br />
<br />
=== Desktop icons rearrange themselves ===<br />
<br />
At certain events (such as opening the panel settings dialog) icons on the desktop rearrange themselves. This is because icon positions are determined by files in the {{ic|~/.config/xfce4/desktop/}} directory. Each time a change is made to the desktop (icons are added or removed or change position) a new file is generated in this directory and these files can conflict.<br />
<br />
To solve the problem, navigate to the directory and delete all the files other than the one which correctly defines the icon positions. You can determine which file defines the correct icon positions by opening it and examining the locations of the icons. The topmost row is defined as {{ic|row 0}} and the leftmost column is defined by {{ic|col 0}}. Therefore an entry of:<br />
<br />
[Firefox]<br />
row=3<br />
col=0<br />
<br />
means that the Firefox icon will be located on the 4th row of the leftmost column.<br />
<br />
=== GTK themes not working with multiple monitors ===<br />
<br />
{{Expansion|Which configuration tools? What does ''ceasing to work'' mean? Is it that new themes cannot be selected or that themes display incorrectly? Is there a bug report?}}<br />
<br />
Some configuration tools may corrupt displays.xml, which results in GTK themes under ''Applications Menu > Settings > Appearance'' ceasing to work. To fix the issue, delete {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml}} and reconfigure your screens.<br />
<br />
=== Icons do not appear in right-click menus ===<br />
<br />
{{Note|Despite the deprecation of GConf, this method does still work.}}<br />
<br />
Users may find that icons do not appear when right-clicking options within some applications, including those made with [[Qt]]. This problem only appears to happen within Xfce. Run these two commands:<br />
<br />
$ gconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true<br />
$ gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true<br />
<br />
=== NVIDIA and xfce4-sensors-plugin ===<br />
<br />
To detect and use sensors of nvidia gpu you need to install {{Pkg|libxnvctrl}} and then rebuild {{Pkg|xfce4-sensors-plugin}} with [[ABS]]. You also have the option of using {{AUR|xfce4-sensors-plugin-nvidia}} which replaces {{Pkg|xfce4-sensors-plugin}}.<br />
<br />
=== Black screens at boot with NVIDIA and multiple monitors ===<br />
<br />
Using [[NVIDIA]], multiple monitors and [[NVIDIA/Troubleshooting#Avoid screen tearing]] may result as a black screen when booting Xfce. The screens' position conflict into the files {{ic|/etc/X11/xorg.conf}} and {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml}}. Deleting the {{ic|displays.xml}} file fixes the behavior.<br />
$ rm ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml<br />
<br />
=== Panel applets keep being aligned on the left ===<br />
<br />
Add a separator someplace before the right end and set its "expand" property. [https://forums.linuxmint.com/viewtopic.php?f=110&t=155602}]<br />
<br />
=== Preferred Applications preferences have no effect ===<br />
<br />
Most applications rely on [[xdg-open]] for opening a preferred application for a given file or URL.<br />
<br />
In order for xdg-open and xdg-settings to detect and integrate with the Xfce desktop environment correctly, you need to [[install]] the {{Pkg|xorg-xprop}} package.<br />
<br />
If you do not do that, your preferred applications preferences (set by exo-preferred-applications) will not be obeyed.<br />
Installing the package and allowing ''xdg-open'' to detect that you are running Xfce makes it forward all calls to ''exo-open'' instead, which correctly uses all your preferred applications preferences.<br />
<br />
To make sure xdg-open integration is working correctly, ask ''xdg-settings'' for the default web browser and see what the result is:<br />
<br />
# xdg-settings get default-web-browser<br />
<br />
If it replies with:<br />
<br />
xdg-settings: unknown desktop environment<br />
<br />
it means that it has failed to detect Xfce as your desktop environment, which is likely due to a missing {{Pkg|xorg-xprop}} package.<br />
<br />
=== Restore default settings ===<br />
<br />
If for any reason you need to revert back: to the default settings, rename {{ic|~/.config/xfce4-session/}} and {{ic|~/.config/xfce4/}}<br />
<br />
$ mv ~/.config/xfce4-session/ ~/.config/xfce4-session-bak<br />
$ mv ~/.config/xfce4/ ~/.config/xfce4-bak<br />
<br />
Relogin for changes to take effect. If you get {{ic|Unable to load a failsafe session}} upon login, see the [[#Session failure]] section.<br />
<br />
=== Session failure ===<br />
<br />
Symptoms include:<br />
<br />
* The mouse is an X and/or does not appear at all;<br />
* Window decorations have disappeared and windows cannot be closed;<br />
* ({{ic|xfwm4-settings}}) will not start, reporting {{ic|These settings cannot work with your current window manager (unknown)}};<br />
* Errors reported by a [[display manager]] such as {{ic|No window manager registered on screen 0}}.<br />
* Unable to load a failsafe session:<br />
<br />
Unable to load a failsafe session.<br />
Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly. <br />
<br />
Restarting Xfce or rebooting your system may solve the problem, but a corrupt session could also be the cause. Delete the session folder:<br />
<br />
$ rm -r ~/.cache/sessions/<br />
<br />
Also make sure that the relevant folders in {{ic|$HOME}} are owned by the user starting {{ic|xfce4}}. See [[Chown]].<br />
<br />
=== Fonts in window title crashing xfce4-title ===<br />
<br />
Install {{Pkg|ttf-droid}} and {{Pkg|ttf-dejavu}}. See also {{Bug|44382}}.<br />
<br />
=== Laptop lid settings ignored ===<br />
<br />
You may find that the lid close settings in Xfce4 Power Manager are ignored, meaning that the laptop will always suspend on lid close, no matter what settings are chosen in the power manager. This is because the power manager is not set to handle lid close events by default. Instead, ''systemd-logind'' handles the lid close event. To change this behavior so that the power manager handles lid close events, execute the following command:<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s false<br />
<br />
{{Note|Under some circumstances, the {{ic|logind-handle-lid-switch}} setting will get set to true when changes are made to the laptop lid actions or the lock on suspend setting. See [https://bugzilla.xfce.org/show_bug.cgi?id&#61;12756#c2]. In this case, you will need to toggle {{ic|logind-handle-lid-switch}} to false again.}}<br />
<br />
=== User switching action button is greyed out ===<br />
<br />
The ''Switch User'' action button assumes that the ''gdmflexiserver'' executable (provided by [[GDM]]) exists. Thus, if GDM is not being used then the button will be greyed out. See the [https://bugzilla.xfce.org/show_bug.cgi?id=9307 upstream bug report].<br />
<br />
A possible workaround is to create an executable script called ''gdmflexiserver'' in {{ic|/usr/bin}} or {{ic|/usr/local/bin}} which calls the greeter switch command provided by the [[display manager]] which is being used.<br />
<br />
* For LXDM - [[LXDM#Simultaneous users and switching users]].<br />
* For LightDM - [[LightDM#User switching]].<br />
<br />
=== Macros in .Xresources not working ===<br />
<br />
Xfce loads {{ic|$HOME/.Xresources}} file using {{ic|xrdb}}, but with {{ic|-nocpp}} option to skip preprocessing. For macros to work properly, copy {{ic|/etc/xdg/xfce4/xinitrc}} to {{ic|$HOME/.config/xfce4}} directory and remove {{ic|-nocpp}} option to {{ic|xrdb}} from the resulting file. See [https://bbs.archlinux.org/profile.php?id=104121 this thread].<br />
<br />
=== Cursor theme doesn't change on login ===<br />
<br />
Ensure the systemwide XDG cursor is set to your desired cursor theme - see [[Cursor themes#XDG specification]].<br />
<br />
== See also ==<br />
<br />
* [http://docs.xfce.org/ Xfce - Documentation]<br />
* [http://wiki.xfce.org Xfce - Wiki]<br />
* [http://www.xfce.org/about/ Xfce - About]<br />
* [https://xfce.org/about/tour Xfce - Tour]<br />
* [[Wikipedia:Xfce]]<br />
* [http://www.xfce-look.org/ Xfce-Look] - Themes, wallpapers, and more.<br />
* [http://xfce.wikia.com/wiki/Main_Page Xfce Wikia]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=User:Sistematico&diff=580351User:Sistematico2019-08-18T20:23:21Z<p>Sistematico: </p>
<hr />
<div>Name: Lucas Saliés Brum<br />
<br />
IRC: sistematico <br />
<br />
Telegram: [https://t.me/sistematico @sistematico]<br />
== My links ==<br />
<br />
* [https://forum.archlinux-br.org/profile.php?id=529 Profile on Arch Linux Brasil]<br />
* [https://sistematico.github.io Github]<br />
* [https://sistematico.gitlab.io Gitlab]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=User:Sistematico&diff=580350User:Sistematico2019-08-18T20:22:36Z<p>Sistematico: Initial page</p>
<hr />
<div>Name: Lucas Saliés Brum<br />
IRC: sistematico<br />
Telegram: * [https://t.me/sistematico @sistematico]<br />
== My links ==<br />
<br />
* [https://forum.archlinux-br.org/profile.php?id=529 Profile on Arch Linux Brasil]<br />
* [https://sistematico.github.io Github]<br />
* [https://sistematico.gitlab.io Gitlab]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Xfce_(Portugu%C3%AAs)&diff=580348Xfce (Português)2019-08-18T20:12:04Z<p>Sistematico: Template copied from https://wiki.archlinux.org/index.php?title=Xfce</p>
<hr />
<div>[[Category:Xfce]]<br />
[[cs:Xfce]]<br />
[[de:Xfce]]<br />
[[es:Xfce]]<br />
[[fa:Xfce]]<br />
[[fr:Xfce]]<br />
[[it:Xfce]]<br />
[[ja:Xfce]]<br />
[[ko:Xfce]]<br />
[[pl:Xfce]]<br />
[[ru:Xfce]]<br />
[[zh-hans:Xfce]]<br />
{{Related articles start}}<br />
{{Related|Desktop environment}}<br />
{{Related|Window manager}}<br />
{{Related|Xfwm}}<br />
{{Related|Thunar}}<br />
{{Related|LXDE}}<br />
{{Related|GNOME}}<br />
{{Related articles end}}<br />
<br />
[http://www.xfce.org Xfce] is a lightweight and modular [[desktop environment]] currently based on both GTK 2 and GTK 3. To provide a complete user experience, it includes a window manager, a file manager, desktop and panel.<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Grp|xfce4}} group. You may also wish to install the {{Grp|xfce4-goodies}} group which includes extra plugins and a number of useful utilities such as the {{Pkg|mousepad}} editor. Xfce uses the [[Xfwm]] window manager by default.<br />
<br />
== Starting ==<br />
<br />
Choose ''Xfce Session'' from the menu in a [[display manager]] of choice, or add {{ic|exec startxfce4}} to [[Xinitrc]].<br />
<br />
{{Note|Do not call the {{ic|xfce4-session}} executable directly; {{ic|startxfce4}} is the correct command which, in turn, calls the former when appropriate.}}<br />
<br />
== Configuration ==<br />
<br />
Xfce stores configuration options in [http://docs.xfce.org/xfce/xfconf/start Xfconf]. There are several ways to modify these options:<br />
<br />
* In the main menu, select [http://docs.xfce.org/xfce/xfce4-settings/start Settings] and the category you want to customize. Categories are programs usually located in {{ic|/usr/bin/xfce4-*}} and {{ic|/usr/bin/xfdesktop-settings}}.<br />
* {{ic|xfce4-settings-editor}} can see and modify all settings. Options modified here will take effect immediately. Use {{ic|xfconf-query}} to change settings from the commandline; see [http://docs.xfce.org/xfce/xfconf/xfconf-query the documentation] for details.<br />
* Settings are stored in XML files in {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/}} which can be edited by hand. However, changes made here will ''not'' take effect immediately.<br />
<br />
=== Menu ===<br />
<br />
See [[Xdg-menu]] for more info on using the Free Desktop menu system.<br />
<br />
==== Whisker menu ====<br />
<br />
{{Pkg|xfce4-whiskermenu-plugin}} (also part of {{Grp|xfce4-goodies}}) is an alternative application launcher. It shows a list of favorites, browses through all installed applications through category buttons, and supports fuzzy searching. After package being installed, it can replace ''Applications Menu'' as first item in Panel 1 (in ''Settings > Panel > Items'' add ''Whisker Menu'').<br />
<br />
==== Edit entries ====<br />
<br />
A number of graphical tools are available for this task:<br />
<br />
* {{App|MenuLibre|An advanced menu editor that provides modern features in a clean, easy-to-use interface.|https://launchpad.net/menulibre|{{AUR|menulibre}}}}.<br />
* {{App|Alacarte|Menu editor for GNOME|http://www.gnome.org/|{{Pkg|alacarte}}}}<br />
* {{App|XAME (XFCE Applications Menu Editor)|GUI tool written in Gambas designed specifically for editing menu entries in Xfce, it will not work in other environments. (Discontinued)|http://redsquirrel87.altervista.org/doku.php/xfce-applications-menu-editor|{{AUR|xame}}}}<br />
<br />
Alternatively, create the file {{ic|~/.config/menus/xfce-applications.menu}} manually. See the example configuration below:<br />
<br />
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"<br />
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd"><br />
<br />
<Menu><br />
<Name>Xfce</Name><br />
<MergeFile type="parent">/etc/xdg/menus/xfce-applications.menu</MergeFile><br />
<br />
<Exclude><br />
<Filename>xfce4-run.desktop</Filename><br />
<Filename>exo-terminal-emulator.desktop</Filename><br />
<Filename>exo-file-manager.desktop</Filename><br />
<Filename>exo-mail-reader.desktop</Filename><br />
<Filename>exo-web-browser.desktop</Filename><br />
<Filename>xfce4-about.desktop</Filename><br />
<Filename>xfhelp4.desktop</Filename><br />
</Exclude><br />
<br />
<Layout><br />
<Merge type="all"/><br />
<Separator/><br />
<Menuname>Settings</Menuname><br />
<Separator/><br />
<Filename>xfce4-session-logout.desktop</Filename><br />
</Layout><br />
</Menu><br />
<br />
The {{ic|<MergeFile>}} tag includes the default Xfce menu.<br />
<br />
The {{ic|<Exclude>}} tag excludes applications which we do not want to appear in the menu. Here we excluded some Xfce default shortcuts, but you can exclude {{ic|firefox.desktop}} or any other application.<br />
<br />
The {{ic|<Layout>}} tag defines the layout of the menu. The applications can be organized in folders or however we wish. For more details see the [http://wiki.xfce.org/howto/customize-menu Xfce wiki].<br />
<br />
You can also make changes to the Xfce menu by editing the {{ic|.desktop}} files themselves. To hide entries, see [[Desktop entries#Hide desktop entries]]. You can edit the application's category by modifying the {{ic|1=Categories=}} line of the desktop entry, see [[Desktop entries#File example]].<br />
<br />
=== Desktop ===<br />
<br />
==== Transparent background for icon titles ====<br />
<br />
To change the default white background of desktop icon titles to something more suitable, create or edit {{ic|~/.gtkrc-2.0}}:<br />
<br />
{{bc|<nowiki><br />
style "xfdesktop-icon-view" {<br />
XfdesktopIconView::label-alpha = 10<br />
base[NORMAL] = "#000000"<br />
base[SELECTED] = "#71B9FF"<br />
base[ACTIVE] = "#71B9FF"<br />
fg[NORMAL] = "#fcfcfc"<br />
fg[SELECTED] = "#ffffff"<br />
fg[ACTIVE] = "#ffffff"<br />
}<br />
widget_class "*XfdesktopIconView*" style "xfdesktop-icon-view"<br />
</nowiki>}}<br />
<br />
==== Remove desktop icons ====<br />
<br />
Issue the following command:<br />
<br />
$ xfconf-query -c xfce4-desktop -v --create -p /desktop-icons/style -t int -s 0<br />
<br />
To reinstate icons on the desktop, issue the same command with a value of 2.<br />
<br />
==== One wallpaper across multihead ====<br />
<br />
Open {{ic|xfce4-settings-editor}} and create a new property with the following settings:<br />
<br />
Property: /backdrop/screen0/xinerama-stretch<br />
Type: Boolean<br />
Value: TRUE|1|Enabled<br />
<br />
==== Kill window shortcut ====<br />
<br />
Xfce does not have a shortcut to kill a window, for example when a program freezes.<br />
<br />
With {{Pkg|xorg-xkill}}, use {{ic|xkill}} to interactively kill a window. For the currently active window, use {{Pkg|xdotool}}:<br />
<br />
$ xdotool getwindowfocus windowkill<br />
<br />
Alternatively:<br />
<br />
$ sh -c "xkill -id $(xprop -root -notype | sed -n '/^_NET_ACTIVE_WINDOW/ s/^.*# *\|\,.*$//g p')"<br />
<br />
To add the shortcut, use ''Settings > Keyboard'' or an application like {{pkg|xbindkeys}}.<br />
<br />
=== Session ===<br />
<br />
==== Autostart ====<br />
<br />
To launch custom applications when Xfce starts up, click the ''Applications Menu > Settings > Settings Manager'' and then choose the ''Session and Startup'' option and click the tab ''Application Autostart''.<br />
You will see a list of programs that get launched on startup. To add an entry, click the ''Add'' button and fill out the form, specifying the path to an executable you want to run.<br />
<br />
Autostart applications are stored as {{ic|''name''.desktop}} in {{ic|~/.config/autostart/}}.<br />
<br />
Alternatively, add the commands you wish to run (including setting environment variables) to [[xinitrc]] (or [[xprofile]] when a [[display manager]] is being used).<br />
<br />
{{Tip|Sometimes it might be useful to '''delay the startup of an application'''. Note that specifying under ''Application > Autostart'' a command such as {{ic|sleep 3 && ''command''}} does not work; a workaround is to use the syntax {{ic|sh -c "sleep 3 && ''command''"}}<br />
}}<br />
<br />
==== Lock the screen ====<br />
''xflock4'' is the reference Bash script which is used to lock an Xfce session.<br />
<br />
It tries to lock the screen with either {{Pkg|xscreensaver}}, {{Pkg|gnome-screensaver}}, {{Pkg|slock}} or {{Pkg|xlockmore}}. It consecutively looks for the corresponding binary or exits with return code 1 if it fails to find any of these four. <br />
<br />
The [[List of applications/Security#Screen lockers]] contains a short description of these four screen lockers together with other popular applications. There is in this list an alternative locker, {{Pkg|light-locker}}, which integrates particularly well with {{Pkg|xfce4-power-manager}}. Once it is installed, Xfce Power Manager's setting gains an additional ''Security'' tab to configure ''light-locker'' and the existing ''Lock screen when system is going for sleep'' setting is relocated under this tab. In this new GUI it is possible to set whether the session should be locked upon screensaver activity or whenever the system goes to sleep.<br />
<br />
To have ''xflock4'' run ''light-locker'' or any custom session locker, not among the four cited above, one must set {{ic|LockCommand}} in the session's xfconf channel to the command line to be used (the command inside the quotes in the following example can be adapted accordingly for other screen lockers):<br />
<br />
{{bc|$ xfconf-query -c xfce4-session -p /general/LockCommand -s "''light-locker-command --lock''" --create -t string}}<br />
<br />
The panel lock button in the ''Action Buttons'' panel simply executes {{ic|/usr/bin/xflock4}}. It should work as expected as long as ''xflock4'' is functioning i.e. one of the native lockers is installed or a custom locker is configured to integrate with it as proposed above.<br />
<br />
==== Suspend ====<br />
Whenever asked to suspend, Xfce executes the {{man|1|xfce4-session-logout}} command with the {{ic|suspend}} option:<br />
<br />
$ xfce4-session-logout --suspend<br />
<br />
Whether or not the session is systematically locked on ''suspend'' can be configured through the xfconf properties or from the GUI.<br />
<br />
To control this state using the CLI: there are two settings that are used, {{ic|LockScreen}} and {{ic|lock-screen-suspend-hibernate}}, in respectively the session and the power manager xfconf channels.<br />
To prevent locking on suspend, turn them to {{ic|false}}:<br />
$ xfconf-query -c xfce4-session -p /shutdown/LockScreen -s '''false'''<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/lock-screen-suspend-hibernate -s '''false'''<br />
Similarly, turn them to {{ic|true}} to lock the session on suspend.<br />
<br />
The setting can also be controlled from the GUI: open the ''Session and Startup'' application and turn the flag ''Advanced > Lock screen before sleep'' on or off.<br />
<br />
Whenever the suspend keyboard button is pressed, it can be handled by either Xfce's power manager or by ''systemd-logind''. To give precedence to logind, the following xfconf setting must be set to {{ic|true}}:<br />
<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-suspend-key -n -t bool -s '''true'''<br />
<br />
{{Note|To check how ''systemd-logind'' handles events whenever it has precedence over Xfce, check {{man|5|logind.conf}}}}<br />
<br />
==== Disable saved sessions ====<br />
<br />
Per user, saved sessions can be disabled by executing the following:<br />
$ xfconf-query -c xfce4-session -p /general/SaveOnExit -s false<br />
Then navigate to ''Applications > Settings > Session and Startup > Sessions'' and press the ''Clear saved sessions'' button to remove all previously saved sessions.<br />
<br />
{{Tip|If the command above does not change the setting persistently, use the following command instead: {{ic|xfconf-query -c xfce4-session -p /general/SaveOnExit -n -t bool -s false}}}}<br />
<br />
Alternatively, Xfce [https://wiki.xfce.org/howto/kiosk_mode kiosk mode] can be used to disable the saving of sessions systemwide. To disable sessions, create or edit the file {{ic|/etc/xdg/xfce4/kiosk/kioskrc}} and add the following:<br />
<br />
[xfce4-session]<br />
SaveSession=NONE<br />
<br />
If kiosk mode is not working, the user can set read only permissions for the sessions directory:<br />
<br />
$ rm ~/.cache/sessions/* && chmod 500 ~/.cache/sessions<br />
<br />
This will prevent Xfce from saving any sessions despite any configuration that specifies otherwise.<br />
<br />
==== Use a different window manager ====<br />
<br />
{{Note|For the changes to take effect, you will need to clear the saved sessions and ensure that session saving is disabled when logging out for the first time. Once the window manager of choice is running, session saving can be enabled again.}}<br />
<br />
The files specifying the default window manager are found in the following locations:<br />
*{{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}} - per user<br />
*{{ic|/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}} - systemwide<br />
<br />
The default window manager for the user can be set easily using ''xfconf-query'':<br />
$ xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -sa ''wm_name''<br />
<br />
If you want to start the window manager with command line options, see the command below:<br />
$ xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -t string -s ''wm_name'' -s ''--wm-option''<br />
If you need more command line options, simply add more {{ic|-t string}} and {{ic|-s ''--wm-option''}} arguments to the command.<br />
<br />
If you want to change the default window manager systemwide, edit the file specified above manually, changing ''xfwm4'' to the preferred window manager and adding more {{ic|1=<value type="string" value="''--wm-option''"/>}} lines for extra command line options if needed.<br />
<br />
You can also change the window manager by autostarting {{ic|''wm_name'' --replace}} using the autostart facility or by running {{ic|''wm_name'' --replace &}} in a terminal and making sure the session is saved on logout. Be aware though that this method does not truly change the default manager, it merely replaces it at login. Note that if you are using the autostart facility, you should disable saved sessions as this could lead to the new window manager being started twice after the default window manager.<br />
<br />
=== Theming ===<br />
<br />
XFCE themes are available at [http://www.xfce-look.org xfce-look.org]. ''Xfwm'' themes are stored in {{ic|/usr/share/themes/xfce4}}, and set in ''Settings > Window Manager''. [[GTK]] themes are set in ''Settings > Appearance''.<br />
<br />
To achieve a uniform look for all applications, see [[Uniform look for Qt and GTK applications]].<br />
<br />
See also [[Cursor themes]], [[Icons]], and [[Font configuration]].<br />
<br />
=== Sound ===<br />
<br />
==== Sound themes ====<br />
<br />
XFCE4 supports [https://www.freedesktop.org/wiki/Specifications/sound-theme-spec/ freedesktop system sounds], but it is not configured out of the box.<br />
<br />
To enable a sound theme:<br />
<br />
# Install {{Pkg|libcanberra}} and {{Pkg|libcanberra-pulse}} for [[PulseAudio]] support;<br />
# "canberra-gtk-module" should be in the GTK_MODULES environment variable (re-login may be required);<br />
# Check "Enable event sounds" in Settings Manager → Appearance → Settings tab;<br />
# In the Settings Editor set "xsettings/Net/SoundThemeName" to a sound theme located in {{Ic|/usr/share/sounds/}};<br />
# Turn on "System Sounds" in audio mixer (e.g. pavucontrol).<br />
<br />
{{Pkg|sound-theme-freedesktop}} provides a compatible sound theme, but it lacks many required events. A better choice is {{AUR|sound-theme-smooth}} (SoundThemeName should be "Smooth").<br />
<br />
==== Keyboard volume buttons ====<br />
<br />
{{Pkg|xfce4-pulseaudio-plugin}} provides a panel applet which has support for keyboard volume control and volume notifications. As an alternative, you can install {{AUR|xfce4-volumed-pulse}}, which also provides keybinding and notification control, but without an icon sitting in the panel. This is handy, for example, when using {{Pkg|pasystray}} at the same time for a finer control.<br />
<br />
Alternatively, {{AUR|xfce4-mixer}} also provides a panel applet and keyboard shortcuts which supports Alsa as well. Note however, that it is based on a feature of GStreamer 0.10 which has been abandoned in 1.0.<br />
<br />
For non desktop environment specific alternatives, see [[List of applications/Multimedia#Volume control]].<br />
<br />
===== Shortcuts =====<br />
<br />
If you are not using an applet or daemon that controls the volume keys, you can map volume control commands to your volume keys manually using Xfce's keyboard settings. For the sound system you are using, see the sections linked to below for the appropriate commands.<br />
*ALSA: see [[Advanced Linux Sound Architecture#Keyboard volume control]].<br />
*PulseAudio: see [[PulseAudio#Keyboard volume control]]<br />
*OSS: see [[OSS#Using multimedia keys with OSS]].<br />
<br />
=== Keyboard Shortcuts ===<br />
<br />
Keyboard shortcuts are defined in two places: ''Settings > Window Manager > Keyboard'', and ''Settings > Keyboard > Shortcuts''.<br />
<br />
=== Polkit Authentication Agent ===<br />
<br />
The {{Pkg|polkit-gnome}} agent will be installed along with {{Pkg|xfce4-session}} and autostarted automatically; no user intervention is required. For more information, see [[Polkit#Authentication agents]].<br />
<br />
A third party polkit authentication agent for Xfce is also available, see {{AUR|xfce-polkit}} or {{AUR|xfce-polkit-git}}.<br />
<br />
=== Display blanking ===<br />
Some programs that are commonly used with Xfce will control monitor blanking and [[DPMS]] (monitor powersaving) settings. They are discussed below.<br />
<br />
;Xfce Power Manager<br />
''Xfce Power Manager'' controls blanking and DPMS settings. These settings can be configured in the ''Power Manager'' GUI within the ''Display'' tab.<br />
<br />
Note that when ''Display power management'' is turned off, DPMS is fully disabled, it does not mean that ''Power Manager'' will simply stop controlling DPMS. It does not disable screen blanking either. To disable both blanking and DPMS, right click on the power manager system tray icon or left click on the panel applet and make sure that the option labelled ''Presentation mode'' is ticked.<br />
<br />
;XScreenSaver<br />
If {{pkg|xscreensaver}} is installed and runs alongside Xfce Power Manager, it may not be clear which application is in control of blanking and DPMS as both are competing for control of the same settings. Therefore, in a situation where it is important that the monitor not be blanked (when watching a video for instance), it is advisable to disable blanking and DPMS through both applications. To know more about ''XScreenSaver'' options, see [[XScreenSaver#DPMS and blanking settings]].<br />
<br />
;xset<br />
If neither of the above applications are running, then blanking and DPMS settings can be controlled using the ''xset'' command, see [[DPMS#Modify DPMS and screensaver settings with a command]].<br />
<br />
{{Note|1=There are some issues associated with blanking and resuming from blanking in some configurations. See [https://bbs.archlinux.org/viewtopic.php?id=194313&p=2][https://bugzilla.xfce.org/show_bug.cgi?id=11107].}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Hide partitions from thunar and xfdesktop ===<br />
<br />
If your installation partitions are shown as mounted devices on the desktop and in Thunar, try to install {{Pkg|gvfs}}. See [[Udisks#Hide selected partitions]] for more advanced configuration options.<br />
<br />
=== Screenshots ===<br />
<br />
Xfce has its own screenshot tool, {{pkg|xfce4-screenshooter}}. It is part of the {{grp|xfce4-goodies}} group.<br />
<br />
Go to ''Applications > Settings > Keyboard'', ''Application Shortcuts''. Add the {{ic|xfce4-screenshooter -f}} (or {{ic|-w}} for the active window) command to use the {{ic|Print}} key in order to take fullscreen screenshots. See screenshooter's man page for other optional arguments.<br />
<br />
Alternatively, an independent screenshot program like [[Taking a screenshot#scrot|scrot]] can be used.<br />
<br />
=== Disable Terminal F1 and F11 shortcuts ===<br />
<br />
The xfce terminal binds F1 and F11 to help and fullscreen, respectively, which can make using programs like htop difficult. To disable those shortcuts, create or edit its configuration file, then log out and log back in. F10 can disabled in the Preferences menu.<br />
<br />
{{hc|~/.config/xfce4/terminal/accels.scm|<br />
(gtk_accel_path "<Actions>/terminal-window/fullscreen" "")<br />
(gtk_accel_path "<Actions>/terminal-window/contents" "")<br />
}}<br />
<br />
=== Terminal color themes or palettes ===<br />
<br />
Terminal color themes or palettes can be changed in GUI under Appearance tab in Preferences. These are the colors that are available to most console applications like [[Emacs]], [[Vi]] and so on. Their settings are stored individually for each system user in {{ic|~/.config/xfce4/terminal/terminalrc}} file. There are also so many other themes to choose from. Check forum thread [https://bbs.archlinux.org/viewtopic.php?id=51818 Terminal Colour Scheme Screenshots] for hundreds of available choices and themes.<br />
<br />
==== Changing default color theme ====<br />
<br />
Xfce's {{ic|extra/terminal}} package comes with a darker colour palette. To change this, append the following in your terminalrc file for a lighter color theme, that is always visible in darker Terminal backgrounds.<br />
<br />
{{hc|~/.config/xfce4/terminal/terminalrc|2=<br />
ColorPalette5=#38d0fcaaf3a9<br />
ColorPalette4=#e013a0a1612f<br />
ColorPalette2=#d456a81b7b42<br />
ColorPalette6=#ffff7062ffff<br />
ColorPalette3=#7ffff7bd7fff<br />
ColorPalette13=#82108210ffff}}<br />
<br />
==== Terminal tango color theme ====<br />
<br />
To switch to tango color theme, open with your favorite editor<br />
<br />
~/.config/xfce4/terminal/terminalrc<br />
<br />
And add(replace) these lines:<br />
<br />
ColorForeground=White<br />
ColorBackground=#323232323232<br />
ColorPalette1=#2e2e34343636<br />
ColorPalette2=#cccc00000000<br />
ColorPalette3=#4e4e9a9a0606<br />
ColorPalette4=#c4c4a0a00000<br />
ColorPalette5=#34346565a4a4<br />
ColorPalette6=#757550507b7b<br />
ColorPalette7=#060698989a9a<br />
ColorPalette8=#d3d3d7d7cfcf<br />
ColorPalette9=#555557575353<br />
ColorPalette10=#efef29292929<br />
ColorPalette11=#8a8ae2e23434<br />
ColorPalette12=#fcfce9e94f4f<br />
ColorPalette13=#72729f9fcfcf<br />
ColorPalette14=#adad7f7fa8a8<br />
ColorPalette15=#3434e2e2e2e2<br />
ColorPalette16=#eeeeeeeeecec<br />
<br />
=== Open URLs by middle mouse in terminal ===<br />
On update to version 0.8 open URL with middle mouse turned off by default and just paste clip to cursor.<br />
To enable old behavior fix next option in {{ic|${XDG_CONFIG_HOME}/xfce4/terminal/terminalrc}} ({{ic|<nowiki>XDG_CONFIG_HOME=${HOME}/.config</nowiki>}} by default)<br />
{{hc|${XDG_CONFIG_HOME}/xfce4/terminal/terminalrc|<nowiki>[Configuration]<br />
MiscMiddleClickOpensUri=TRUE</nowiki>}}<br />
<br />
=== Colour management ===<br />
<br />
Xfce has no native support for colour management. [https://bugzilla.xfce.org/show_bug.cgi?id=8559] See [[ICC profiles]] for alternatives.<br />
<br />
=== Multiple monitors ===<br />
<br />
Xfce has support for multiple monitors. Settings can be configured in the ''Applications > Settings > Display'' dialog. For more information, see the [http://docs.xfce.org/xfce/xfce4-settings/display display] article from the Xfce documentation.<br />
<br />
XFCE's display configuration is not persistent so you may find yourself needing to use the display tool a lot, especially if you use multiple displays. One workaround for this is to use {{pkg|arandr}} to easily configure your display configurations in the form of xrandr commands which you can assign to be executed as XFCE keyboard shortcuts.<br />
<br />
=== SSH agents ===<br />
<br />
By default Xfce 4.10 will try to load gpg-agent or ssh-agent in that order during session initialization. To disable this, create an xfconf key using the following command:<br />
<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
To force using ssh-agent even if gpg-agent is installed, run the following instead:<br />
<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/type -n -t string -s ssh-agent<br />
<br />
To use [[GNOME Keyring]], simply tick the checkbox ''Launch GNOME services on startup'' in the ''Advanced'' tab of ''Session and Startup'' in Xfce's settings. This will also disable gpg-agent and ssh-agent.<br />
<br />
Source: http://docs.xfce.org/xfce/xfce4-session/advanced<br />
<br />
=== Scroll a background window without shifting focus on it ===<br />
<br />
Go to ''Main Menu > Settings > Window Manager Tweaks > Accessibility'' tab.<br />
Uncheck ''Raise windows when any mouse button is pressed''.<br />
<br />
=== Mouse button modifier ===<br />
<br />
By default, the mouse button modifier in Xfce is set to {{ic|Alt}}. This can be changed with ''xfconf-query''. For instance, the following command will set the {{ic|Super}} key as the mouse button modifier:<br />
<br />
$ xfconf-query -c xfwm4 -p /general/easy_click -n -t string -s "Super"<br />
<br />
Strictly speaking, using multiple modifiers is not supported. However, as a workaround, multiple modifiers can be specified if the key names are separated with {{ic|><}}. For instance, to set {{ic|Ctrl+Alt}} as the mouse button modifier, you can use the following command:<br />
<br />
$ xfconf-query -c xfwm4 -p /general/easy_click -n -t string -s "Ctrl><Alt"<br />
<br />
=== Set the two fingers click to middle click for a touchpad ===<br />
<br />
{{Style|Convoluted way of simply configuring [[Touchpad Synaptics]]}}<br />
<br />
If you want the 2 finger click on the touchpad to do a middle click, create or edit the following file:<br />
<br />
{{hc|~/.config/xfce4/xfconf/xfce-perchannel-xml/pointers.xml|<nowiki><br />
<channel name="pointers" version="1.0"><br />
<property name="SynPS2_Synaptics_TouchPad" type="empty"><br />
<property name="Properties" type="empty"><br />
<property name="Synaptics_Tap_Action" type="array"><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="0"/><br />
<value type="int" value="1"/><br />
<value type="int" value="2"/><br />
<value type="int" value="3"/><br />
</property><br />
</property><br />
</property><br />
</channel><br />
</nowiki>}}<br />
<br />
The 2 in the array is the middle click.<br />
<br />
=== Limit the minimum brightness of the brightness-slider ===<br />
Limiting the minimum brightness can be useful for displays which turn off backlight on a brightness level of 0. In {{ic|xfce4-power-manager 1.3.2}} a new hidden option had been introduced to set a minimum brightness value with a xfconf4-property. Add {{ic|brightness-slider-min-level}} as an int property in xfconf4. Adjust the int value to get a suitable minimum brightness level.<br />
<br />
=== Adding profile pictures ===<br />
To add profile pictures for each user to be displayed in the whisker-menu, simply place a 96x96 PNG file in the respective user's home directory with the name {{ic|.face}}. For example the PNG file {{ic|/home/''bob''/.face}} for user ''bob''.<br />
<br />
Image editing programs like [[GIMP]] can be used to convert and scale your favourite images down to 96x96.<br />
<br />
=== Power manager plugin label ===<br />
<br />
The xfconf option {{ic|show-panel-label}} of type {{ic|int}} controls the label of the power manager, it can be configured for different label formats: it can be set to 0 (no label), 1 (percentage), 2 (remaining time) or 3 (both).<br />
<br />
It is also accessible through the power manager plugin GUI in ''Properties > Show label''<br />
<br />
== Troubleshooting ==<br />
<br />
=== Desktop icons rearrange themselves ===<br />
<br />
At certain events (such as opening the panel settings dialog) icons on the desktop rearrange themselves. This is because icon positions are determined by files in the {{ic|~/.config/xfce4/desktop/}} directory. Each time a change is made to the desktop (icons are added or removed or change position) a new file is generated in this directory and these files can conflict.<br />
<br />
To solve the problem, navigate to the directory and delete all the files other than the one which correctly defines the icon positions. You can determine which file defines the correct icon positions by opening it and examining the locations of the icons. The topmost row is defined as {{ic|row 0}} and the leftmost column is defined by {{ic|col 0}}. Therefore an entry of:<br />
<br />
[Firefox]<br />
row=3<br />
col=0<br />
<br />
means that the Firefox icon will be located on the 4th row of the leftmost column.<br />
<br />
=== GTK themes not working with multiple monitors ===<br />
<br />
{{Expansion|Which configuration tools? What does ''ceasing to work'' mean? Is it that new themes cannot be selected or that themes display incorrectly? Is there a bug report?}}<br />
<br />
Some configuration tools may corrupt displays.xml, which results in GTK themes under ''Applications Menu > Settings > Appearance'' ceasing to work. To fix the issue, delete {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml}} and reconfigure your screens.<br />
<br />
=== Icons do not appear in right-click menus ===<br />
<br />
{{Note|Despite the deprecation of GConf, this method does still work.}}<br />
<br />
Users may find that icons do not appear when right-clicking options within some applications, including those made with [[Qt]]. This problem only appears to happen within Xfce. Run these two commands:<br />
<br />
$ gconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true<br />
$ gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true<br />
<br />
=== NVIDIA and xfce4-sensors-plugin ===<br />
<br />
To detect and use sensors of nvidia gpu you need to install {{Pkg|libxnvctrl}} and then rebuild {{Pkg|xfce4-sensors-plugin}} with [[ABS]]. You also have the option of using {{AUR|xfce4-sensors-plugin-nvidia}} which replaces {{Pkg|xfce4-sensors-plugin}}.<br />
<br />
=== Black screens at boot with NVIDIA and multiple monitors ===<br />
<br />
Using [[NVIDIA]], multiple monitors and [[NVIDIA/Troubleshooting#Avoid screen tearing]] may result as a black screen when booting Xfce. The screens' position conflict into the files {{ic|/etc/X11/xorg.conf}} and {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml}}. Deleting the {{ic|displays.xml}} file fixes the behavior.<br />
$ rm ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml<br />
<br />
=== Panel applets keep being aligned on the left ===<br />
<br />
Add a separator someplace before the right end and set its "expand" property. [https://forums.linuxmint.com/viewtopic.php?f=110&t=155602}]<br />
<br />
=== Preferred Applications preferences have no effect ===<br />
<br />
Most applications rely on [[xdg-open]] for opening a preferred application for a given file or URL.<br />
<br />
In order for xdg-open and xdg-settings to detect and integrate with the Xfce desktop environment correctly, you need to [[install]] the {{Pkg|xorg-xprop}} package.<br />
<br />
If you do not do that, your preferred applications preferences (set by exo-preferred-applications) will not be obeyed.<br />
Installing the package and allowing ''xdg-open'' to detect that you are running Xfce makes it forward all calls to ''exo-open'' instead, which correctly uses all your preferred applications preferences.<br />
<br />
To make sure xdg-open integration is working correctly, ask ''xdg-settings'' for the default web browser and see what the result is:<br />
<br />
# xdg-settings get default-web-browser<br />
<br />
If it replies with:<br />
<br />
xdg-settings: unknown desktop environment<br />
<br />
it means that it has failed to detect Xfce as your desktop environment, which is likely due to a missing {{Pkg|xorg-xprop}} package.<br />
<br />
=== Restore default settings ===<br />
<br />
If for any reason you need to revert back: to the default settings, rename {{ic|~/.config/xfce4-session/}} and {{ic|~/.config/xfce4/}}<br />
<br />
$ mv ~/.config/xfce4-session/ ~/.config/xfce4-session-bak<br />
$ mv ~/.config/xfce4/ ~/.config/xfce4-bak<br />
<br />
Relogin for changes to take effect. If you get {{ic|Unable to load a failsafe session}} upon login, see the [[#Session failure]] section.<br />
<br />
=== Session failure ===<br />
<br />
Symptoms include:<br />
<br />
* The mouse is an X and/or does not appear at all;<br />
* Window decorations have disappeared and windows cannot be closed;<br />
* ({{ic|xfwm4-settings}}) will not start, reporting {{ic|These settings cannot work with your current window manager (unknown)}};<br />
* Errors reported by a [[display manager]] such as {{ic|No window manager registered on screen 0}}.<br />
* Unable to load a failsafe session:<br />
<br />
Unable to load a failsafe session.<br />
Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly. <br />
<br />
Restarting Xfce or rebooting your system may solve the problem, but a corrupt session could also be the cause. Delete the session folder:<br />
<br />
$ rm -r ~/.cache/sessions/<br />
<br />
Also make sure that the relevant folders in {{ic|$HOME}} are owned by the user starting {{ic|xfce4}}. See [[Chown]].<br />
<br />
=== Fonts in window title crashing xfce4-title ===<br />
<br />
Install {{Pkg|ttf-droid}} and {{Pkg|ttf-dejavu}}. See also {{Bug|44382}}.<br />
<br />
=== Laptop lid settings ignored ===<br />
<br />
You may find that the lid close settings in Xfce4 Power Manager are ignored, meaning that the laptop will always suspend on lid close, no matter what settings are chosen in the power manager. This is because the power manager is not set to handle lid close events by default. Instead, ''systemd-logind'' handles the lid close event. To change this behavior so that the power manager handles lid close events, execute the following command:<br />
$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s false<br />
<br />
{{Note|Under some circumstances, the {{ic|logind-handle-lid-switch}} setting will get set to true when changes are made to the laptop lid actions or the lock on suspend setting. See [https://bugzilla.xfce.org/show_bug.cgi?id&#61;12756#c2]. In this case, you will need to toggle {{ic|logind-handle-lid-switch}} to false again.}}<br />
<br />
=== User switching action button is greyed out ===<br />
<br />
The ''Switch User'' action button assumes that the ''gdmflexiserver'' executable (provided by [[GDM]]) exists. Thus, if GDM is not being used then the button will be greyed out. See the [https://bugzilla.xfce.org/show_bug.cgi?id=9307 upstream bug report].<br />
<br />
A possible workaround is to create an executable script called ''gdmflexiserver'' in {{ic|/usr/bin}} or {{ic|/usr/local/bin}} which calls the greeter switch command provided by the [[display manager]] which is being used.<br />
<br />
* For LXDM - [[LXDM#Simultaneous users and switching users]].<br />
* For LightDM - [[LightDM#User switching]].<br />
<br />
=== Macros in .Xresources not working ===<br />
<br />
Xfce loads {{ic|$HOME/.Xresources}} file using {{ic|xrdb}}, but with {{ic|-nocpp}} option to skip preprocessing. For macros to work properly, copy {{ic|/etc/xdg/xfce4/xinitrc}} to {{ic|$HOME/.config/xfce4}} directory and remove {{ic|-nocpp}} option to {{ic|xrdb}} from the resulting file. See [https://bbs.archlinux.org/profile.php?id=104121 this thread].<br />
<br />
=== Cursor theme doesn't change on login ===<br />
<br />
Ensure the systemwide XDG cursor is set to your desired cursor theme - see [[Cursor themes#XDG specification]].<br />
<br />
== See also ==<br />
<br />
* [http://docs.xfce.org/ Xfce - Documentation]<br />
* [http://wiki.xfce.org Xfce - Wiki]<br />
* [http://www.xfce.org/about/ Xfce - About]<br />
* [https://xfce.org/about/tour Xfce - Tour]<br />
* [[Wikipedia:Xfce]]<br />
* [http://www.xfce-look.org/ Xfce-Look] - Themes, wallpapers, and more.<br />
* [http://xfce.wikia.com/wiki/Main_Page Xfce Wikia]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Visual_Studio_Code&diff=508501Visual Studio Code2018-01-25T16:32:55Z<p>Sistematico: Added oficial link to vscode</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Text editors]]<br />
[[ja:Visual Studio Code]]<br />
[[zh-hans:Visual Studio Code]]<br />
[https://code.visualstudio.com/ Visual Studio Code] is a cross-platform, free and open-source (licensed under the MIT License) text editor developed by Microsoft and written in JavaScript and TypeScript. It is built on the Electron framework and is extensible using extensions, which can be browsed from within the text editor itself (via its extension gallery) or from https://marketplace.visualstudio.com/VSCode. While open-source, a proprietary build (licensed under an End-User License Agreement) provided by Microsoft is available and used as the basis for the {{AUR|visual-studio-code-bin}} AUR package (for an explanation of the mixed licensing, see this GitHub [https://github.com/Microsoft/vscode/issues/60#issuecomment-161792005 comment]).<br />
<br />
== Installation ==<br />
The following packages provide VSCode:<br />
<br />
* {{AUR|visual-studio-code-bin}}<br />
* {{AUR|code}}<br />
* {{AUR|code-git}}<br />
<br />
===Debugging C#===<br />
If you want to debug C# code install {{AUR|icu55}} otherwise you will end up with a 'Debug adapter process has terminated unexpectedly' error<br />
<br />
== Usage ==<br />
<br />
Run {{ic|code}}. <br />
<br />
If for any reason you wish to launch multiple instances of Visual Studio Code, the {{ic|-n}} flag can be used.<br />
<br />
==Configuration==<br />
<br />
Visual Studio Code settings are stored in {{ic|~/.config/Code/User/settings.json}}.<br />
<br />
===Integrated Terminal===<br />
<br />
''View > Integrated Terminal'' or {{ic|Ctrl + `}} opens up an integrated terminal.<br />
By default, [[Bash]] is used with no additional arguments, although this can be changed.<br />
{{ic|terminal.integrated.shell.linux}} sets the default shell to be used and<br />
{{ic|terminal.integrated.shellArgs.linux}} sets the arguments to be passed to the shell.<br />
<br />
Example:<br />
<br />
{{hc|~/.config/Code/User/settings.json|<br />
"terminal.integrated.shell.linux": "/usr/bin/fish",<br />
"terminal.integrated.shellArgs.linux": ["-l","-d 3"]<br />
}}<br />
<br />
===External Terminal===<br />
<br />
If you are using '''Terminator''' as default terminal for Arch and you have an error on Visual Studio Code: {{ic|Unable to launch debugger worker process (vsdbg) through the terminal. spawn truecolor ENOENT}}, you can change the terminal that will be used by Visual Studio to another terminal (eg gnome-terminal).<br />
<br />
{{ic|"terminal.external.linuxExec": "Yours alternative terminal"}} sets the default terminal to be used for exec debug.<br />
<br />
Example:<br />
<br />
{{hc|~/.config/Code/User/settings.json|<br />
"terminal.external.linuxExec": "gnome-terminal"<br />
}}</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Dotfiles&diff=507715Dotfiles2018-01-17T23:13:01Z<p>Sistematico: /* changed i3blocks to polybar */</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Dotfiles]]<br />
[[ja:ドットファイル]]<br />
{{Related articles start}}<br />
{{Related|XDG Base Directory support}}<br />
{{Related|X resources}}<br />
{{Related articles end}}<br />
This article collects user repositories with custom configuration files, commonly known as ''dotfiles''.<br />
<br />
== Version control ==<br />
<br />
Managing dotfiles with version control software such as [[Git]] helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.<br />
<br />
=== Using gitignore ===<br />
<br />
Keeping a [https://git-scm.com/blog/2010/04/11/environment.html git directory] inside the home folder allows to directly keep track of changes. It is recommended to selectively add file contents to the index with {{man|1|git-add}}. <br />
<br />
To prevent untracked files (appearing in commits and removed by {{man|1|git-clean}}), first exclude all files with {{man|5|gitignore}}:<br />
<br />
{{hc|~/.git/info/exclude|<br />
*}}<br />
<br />
Then use {{ic|git add -f}}, for example:<br />
<br />
$ git add -f ~/.config/*<br />
<br />
And commit the changes with {{man|1|git-commit}}:<br />
<br />
$ git commit -a<br />
<br />
=== Other tools ===<br />
<br />
* {{App|dotbot|A minimalist dotfiles manager that can be installed as a git submodule of your dotfiles repository.|https://github.com/anishathalye/dotbot}}<br />
* {{App|dotdrop|A tool to manage different versions of your dotfiles on different hosts.|https://github.com/deadc0de6/dotdrop}}<br />
* {{App|dotfiles|A tool to make managing your dotfile symlinks in $HOME easy, allowing you to keep all of them in a single directory.|https://github.com/jbernard/dotfiles|{{AUR|dotfiles}}}}<br />
* {{App|dotgit|A comprehensive solution to managing your dotfiles.|http://github.com/Cube777/dotgit|{{AUR|dotgit}}}}<br />
* {{App|dots|A portable tool for managing a single set of dotfiles in an organized fashion.|https://github.com/EvanPurkhiser/dots|{{AUR|dots-manager}}}}<br />
* {{App|[[etckeeper]]|Intended to version-control system-wide configuration in /etc. Works by keeping track of permissions and modes which version-control software often ignores. Can use various SCM systems as a backend. Hooks can auto-commit changes to the repository before a system-upgrade.|http://etckeeper.branchable.com/|{{Pkg|etckeeper}}}}<br />
* {{App|GNU Stow|Can be used to symlink dotfiles from a repository into the $HOME tree. See [http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] for more information.|http://www.gnu.org/software/stow/|{{Pkg|stow}}}}<br />
* {{App|homeshick|git dotfiles synchronizer written in bash.|https://github.com/andsens/homeshick|{{AUR|homeshick-git}}}}<br />
* {{App|homesick|Your home directory is your castle. Don't leave your dotfiles behind.|https://github.com/technicalpickles/homesick|{{AUR|homesick}}}}<br />
* {{App|mackup|a small Python utitlity to keep your application settings in sync.|https://github.com/lra/mackup|{{AUR|mackup}}}}<br />
* {{App|Pearl|Package manager for dotfiles, plugins, programs and any form of code accessible via git. Allow to easily share and sync packages across systems and have them ready to work out of the box.|https://github.com/pearl-core/pearl|{{AUR|pearl-git}}}}<br />
* {{App|rcm|Can be used to symlink dotfiles from a repository into the $HOME tree.|https://github.com/thoughtbot/rcm|{{AUR|rcm}}}}<br />
* {{App|vcsh|Allows separating differents modules (e.g., Emacs config vs. zsh config) into individual repositories which can be maintained separately, as opposed to keeping all dotfiles in a single repository. Works with git only.|https://github.com/RichiH/vcsh|{{AUR|vcsh}}}}<br />
* {{App|yadm|Manages files across systems using a single Git repository. Provides a way to use alternate files on a specific OS or host. Supplies a method of encrypting confidential data so it can safely be stored in your repository.|https://github.com/TheLocehiliosan/yadm|{{AUR|yadm-git}}}}<br />
<br />
=== Maintaining dotfiles across multiple machines ===<br />
<br />
{{Style|This and the section below need a rewrite}}<br />
<br />
One way of maintaining dotfiles across various machines across various hosts while still allowing for per-host customizations, is by maintaining a master-branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; as shared configuration is added to the master-branch, the per-machine branches are then rebased on top of the updated master.<br />
<br />
Another approach is to put machine-specific configuration into specially commented blocks and to use [https://pypi.python.org/pypi/mir.qualia/ qualia] to automatically uncomment them on each machine. This approach requires less manual work and doesn't cause merge conflicts.<br />
<br />
=== Confidential information ===<br />
<br />
Occasionally, software may keep plain-text passwords in configuration files, as opposed to hooking into a keyring. In these cases, git clean-filters may be handy to avoid accidentally commiting confidential information. E. g., the following file assigns a filter to the file “some-dotfile”:<br />
<br />
{{hc|.gitattributes|<nowiki><br />
some-dotfile filter=remove-pass<br />
</nowiki>}}<br />
<br />
Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in the git-configuration file, e. g.:<br />
<br />
{{hc|.git/config|<nowiki><br />
[filter "remove-pass"]<br />
clean = "sed -e 's/^password=.*/#password=TODO/'"<br />
</nowiki>}}<br />
<br />
== Repositories ==<br />
<br />
{| class="wikitable sortable"<br />
! scope="col" | Author<br />
! scope="col" | Shell (shell framework)<br />
! scope="col" | WM / DE<br />
! scope="col" | Editor<br />
! scope="col" | Terminal<br />
! scope="col" | Multiplexer<br />
! scope="col" | Audio<br />
! scope="col" | Monitor<br />
! scope="col" | Mail<br />
! scope="col" | IRC<br />
|-<br />
! [https://bitbucket.org/ambrevar/dotfiles Ambrevar]<br />
| zsh || awesome || emacs || rxvt-unicode || || cmus || htop/vicious || mutt ||<br />
|-<br />
! [https://github.com/awalGarg/dotfiles awal]<br />
| fish || i3 || vim || sakura || tmux || || i3status || || The Lounge<br />
|-<br />
! [https://github.com/ayekat/dotfiles ayekat]<br />
| zsh || karuiwm || vim || rxvt-unicode || tmux || ncmpcpp/mpd || karuibar || claws-mail/mutt || irssi<br />
|-<br />
! [https://github.com/bamos/dotfiles bamos]<br />
| zsh || i3/xmonad || vim/emacs || rxvt-unicode || tmux || mpv/cmus || conky/xmobar || mutt || ERC<br />
|-<br />
! [https://github.com/pbrisbin/dotfiles brisbin33]<br />
| [https://github.com/pbrisbin/oh-my-zsh zsh] || [https://github.com/pbrisbin/xmonad-config xmonad] || [https://github.com/pbrisbin/vim-config vim] || rxvt-unicode || screen || || dzen || [https://github.com/pbrisbin/mutt-config mutt] || [https://github.com/pbrisbin/irssi-config irssi]<br />
|-<br />
! [https://github.com/cinelli/dotfiles cinelli]<br />
| zsh || dwm || vim || termite-git || || pianobar || htop || mutt-kz || weechat<br />
|-<br />
! [https://github.com/Earnestly/dotfiles Earnestly]<br />
| zsh || i3/orbment || vim/emacs || termite || tmux || mpd || conky || mutt || weechat<br />
|-<br />
! [https://github.com/ErikBjare/dotfiles ErikBjare]<br />
| zsh || xmonad/xfce4 || vim || terminator || tmux || || xfce4-panel || || weechat<br />
|-<br />
! [https://github.com/falconindy/dotfiles falconindy]<br />
| bash || i3 || vim || rxvt-unicode || || ncmpcpp || conky || mutt ||<br />
|-<br />
! [https://github.com/graysky2/configs/tree/master/dotfiles graysky]<br />
| zsh || xfce4 || vim || terminal || || ncmpcpp || custom || thunderbird ||<br />
|-<br />
! [https://github.com/hugdru/dotfiles hugdru]<br />
| zsh || awesome || neovim || rxvt-unicode || tmux || || || thunderbird || weechat<br />
|-<br />
! [https://github.com/insanum/dotfiles insanum]<br />
| bash || herbstluftwm || vim || evilvte || tmux || || dzen || mutt-kz ||<br />
|-<br />
! [https://github.com/izmntuk/archiso/tree/testing/configs/alter/airootfs/ izmntuk]<br />
| zsh || xfce4 || vim || rxvt-unicode/yaft || tmux || cmus || xfce4-panel || || irssi<br />
|-<br />
! [https://bitbucket.org/jasonwryan/shiv/src jasonwryan]<br />
| bash/zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irrsi<br />
|-<br />
! [https://github.com/JDevlieghere/dotfiles/ jdevlieghere]<br />
| zsh || xmonad || vim || terminal || tmux || || htop || mutt || weechat<br />
|-<br />
! [https://github.com/jelly/Dotfiles jelly]<br />
| zsh || i3 || vim || termite || tmux || ncmpcpp || || mutt-kz-git || weechat<br />
|-<br />
! [https://github.com/maximbaz/dotfiles maximbaz]<br />
| zsh || i3-gaps || neovim || alacritty || tmux || || py3status || thunderbird ||<br />
|-<br />
! [https://github.com/meskarune/.dotfiles meskarune]<br />
| bash || herbstluftwm || vim || rxvt-unicode || screen || || conky || || weechat<br />
|-<br />
! [https://github.com/neersighted/dotfiles neersighted]<br />
| zsh || i3 || vim || rxvt-unicode || tmux || ncmpcpp || htop || mutt || irssi<br />
|-<br />
! [https://github.com/ok100/configs OK100]<br />
| bash || dwm || vim || rxvt-unicode || || cmus || conky, dzen || mutt || weechat<br />
|-<br />
! [https://github.com/pid1/dotfiles pid1]<br />
| zsh || dwm || neovim || st || tmux || || custom || mutt || weechat<br />
|-<br />
! [https://github.com/polyzen/dotfiles polyzen]<br />
| zsh || i3 || vim || termite || tmux || || i3status || || weechat<br />
|-<br />
! [https://github.com/sistematico/majestic sistematico]<br />
| zsh/fish/bash || [https://github.com/Airblader/i3 i3 Gaps] || vim/nano || termite || tmux || ncmpcpp || polybar || mutt || weechat<br />
|-<br />
! [https://github.com/swalladge/dotfiles swalladge]<br />
| zsh/bash || i3 || neovim/vim || termite || tmux || cmus || i3pystatus || mutt ||<br />
|-<br />
! [https://github.com/thiagowfx/dotfiles thiagowfx]<br />
| bash/zsh || i3 || vim/emacs || rxvt-unicode || || ncmpcpp || i3blocks || ||<br />
|-<br />
! [http://hg.subtle.de/dotfiles/file unexist]<br />
| zsh || subtle || vim || rxvt-unicode || || ncmpcpp || || mutt || irssi<br />
|-<br />
! [https://github.com/vodik/dotfiles vodik]<br />
| zsh || xmonad || vim || termite-git || tmux || ncmpcpp || custom || mutt || weechat<br />
|-<br />
! [https://github.com/w0ng/dotfiles w0ng]<br />
| zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irssi<br />
|-<br />
! [https://github.com/Wintervenom/Configuration Wintervenom]<br />
| bash || herbstluftwm ||vim || rxvt-unicode || screen ||mpd ([https://github.com/Wintervenom/Scripts/tree/master/audio/mpd mpc-utils]) || [https://github.com/Wintervenom/Scripts/blob/master/wm/herbstluftwm/hlwm-dzen2 hlwm-dzen2] || mutt || weechat<br />
|-<br />
! [https://github.com/wolfcore/dotfiles wolfcore] <br />
| bash || dwm || vim || rxvt-unicode || tmux || cmus || custom || || weechat<br />
|-<br />
! [https://github.com/zendeavor zendeavor]<br />
| [https://github.com/zendeavor/config-stuff/tree/sandbag/zsh zsh] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/config i3] || [https://github.com/zendeavor/dotvim/tree/sandbag vim] || [https://github.com/zendeavor/config-stuff/blob/sandbag/X11/Xresources#L14 rxvt-unicode] || [https://github.com/zendeavor/config-stuff/tree/sandbag/tmux tmux] || [https://github.com/zendeavor/config-stuff/blob/sandbag/ncmpcpp/config ncmpcpp] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/i3status.conf i3status] || || [https://github.com/zendeavor/config-stuff/tree/kiwi/weechat weechat]<br />
|-<br />
! [https://github.com/0n-s/dotfiles dillebidum]<br />
| zsh/mksh || dwm/i3 || vim/vis || st || tmux/dvtm || ncmpcpp/mpv || htop/i3blocks || mutt || ii/irssi<br />
|-<br />
<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[gregswiki:DotFiles]]<br />
* [http://wiki.haskell.org/Xmonad/Config_archive XMonad Config Archive]<br />
* [http://dotshare.it dotshare.it]<br />
* [https://dotfiles.github.io/ dotfiles.github.io]<br />
* [https://terminal.sexy/ terminal.sexy] - Terminal color scheme designer</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Dotfiles&diff=490553Dotfiles2017-09-18T03:17:17Z<p>Sistematico: /* i3 gaps link... */</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Dotfiles]]<br />
[[ja:ドットファイル]]<br />
{{Related articles start}}<br />
{{Related|XDG Base Directory support}}<br />
{{Related articles end}}<br />
This article collects user repositories with custom configuration files, commonly known as ''dotfiles''.<br />
<br />
== Version control ==<br />
<br />
Managing dotfiles with version control software such as [[Git]] helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.<br />
<br />
=== Using gitignore ===<br />
<br />
Keeping a [https://git-scm.com/blog/2010/04/11/environment.html git directory] inside the home folder allows to directly keep track of changes. It is recommended to selectively add file contents to the index with {{man|1|git-add}}. <br />
<br />
To prevent untracked files (appearing in commits and removed by {{man|1|git-clean}}), first exclude all files with {{man|5|gitignore}}:<br />
<br />
{{hc|~/.git/info/exclude|<br />
*}}<br />
<br />
Then use {{ic|git add -f}}, for example:<br />
<br />
$ git add -f ~/.config/*<br />
<br />
And commit the changes with {{man|1|git-commit}}:<br />
<br />
$ git commit -a<br />
<br />
=== Other tools ===<br />
<br />
* {{App|dotbot|A minimalist dotfiles manager that can be installed as a git submodule of your dotfiles repository.|https://github.com/anishathalye/dotbot}}<br />
* {{App|dotdrop|A tool to manage different versions of your dotfiles on different hosts.|https://github.com/deadc0de6/dotdrop}}<br />
* {{App|dotfiles|A tool to make managing your dotfile symlinks in $HOME easy, allowing you to keep all of them in a single directory.|https://github.com/jbernard/dotfiles|{{AUR|dotfiles}}}}<br />
* {{App|dotgit|A comprehensive solution to managing your dotfiles.|http://github.com/Cube777/dotgit|{{AUR|dotgit}}}}<br />
* {{App|dots|A portable tool for managing a single set of dotfiles in an organized fashion.|https://github.com/EvanPurkhiser/dots|{{AUR|dots-manager}}}}<br />
* {{App|[[etckeeper]]|Intended to version-control system-wide configuration in /etc. Works by keeping track of permissions and modes which version-control software often ignores. Can use various SCM systems as a backend. Hooks can auto-commit changes to the repository before a system-upgrade.|http://etckeeper.branchable.com/|{{Pkg|etckeeper}}}}<br />
* {{App|GNU Stow|Can be used to symlink dotfiles from a repository into the $HOME tree. See [http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] for more information.|http://www.gnu.org/software/stow/|{{Pkg|stow}}}}<br />
* {{App|homeshick|git dotfiles synchronizer written in bash.|https://github.com/andsens/homeshick|{{AUR|homeshick-git}}}}<br />
* {{App|homesick|Your home directory is your castle. Don't leave your dotfiles behind.|https://github.com/technicalpickles/homesick|{{AUR|homesick}}}}<br />
* {{App|mackup|a small Python utitlity to keep your application settings in sync.|https://github.com/lra/mackup|{{AUR|mackup}}}}<br />
* {{App|Pearl|Package manager for dotfiles, plugins, programs and any form of code accessible via git. Allow to easily share and sync packages across systems and have them ready to work out of the box.|https://github.com/pearl-core/pearl|{{AUR|pearl-git}}}}<br />
* {{App|rcm|Can be used to symlink dotfiles from a repository into the $HOME tree.|https://github.com/thoughtbot/rcm|{{AUR|rcm}}}}<br />
* {{App|vcsh|Allows separating differents modules (e.g., Emacs config vs. zsh config) into individual repositories which can be maintained separately, as opposed to keeping all dotfiles in a single repository. Works with git only.|https://github.com/RichiH/vcsh|{{AUR|vcsh}}}}<br />
* {{App|yadm|Manages files across systems using a single Git repository. Provides a way to use alternate files on a specific OS or host. Supplies a method of encrypting confidential data so it can safely be stored in your repository.|https://github.com/TheLocehiliosan/yadm|{{AUR|yadm-git}}}}<br />
<br />
=== Maintaining dotfiles across multiple machines ===<br />
<br />
{{Style|This and the section below need a rewrite}}<br />
<br />
One way of maintaining dotfiles across various machines across various hosts while still allowing for per-host customizations, is by maintaining a master-branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; as shared configuration is added to the master-branch, the per-machine branches are then rebased on top of the updated master.<br />
<br />
Another approach is to put machine-specific configuration into specially commented blocks and to use [https://pypi.python.org/pypi/mir.qualia/ qualia] to automatically uncomment them on each machine. This approach requires less manual work and doesn't cause merge conflicts.<br />
<br />
=== Confidential information ===<br />
<br />
Occasionally, software may keep plain-text passwords in configuration files, as opposed to hooking into a keyring. In these cases, git clean-filters may be handy to avoid accidentally commiting confidential information. E. g., the following .gitattributes file assigns a filter to the file “some-dotfile”:<br />
<br />
# .gitattributes<br />
some-dotfile filter=remove-pass<br />
<br />
Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in {{ic|.git/config}}, e. g.:<br />
<br />
[filter "remove-pass"]<br />
clean = "sed -e 's/^password=.*/#password=TODO/'"<br />
<br />
== Repositories ==<br />
<br />
{| class="wikitable sortable"<br />
! scope="col" | Author<br />
! scope="col" | Shell (shell framework)<br />
! scope="col" | WM / DE<br />
! scope="col" | Editor<br />
! scope="col" | Terminal<br />
! scope="col" | Multiplexer<br />
! scope="col" | Audio<br />
! scope="col" | Monitor<br />
! scope="col" | Mail<br />
! scope="col" | IRC<br />
|-<br />
! [https://bitbucket.org/ambrevar/dotfiles Ambrevar]<br />
| zsh || awesome || emacs || rxvt-unicode || || cmus || htop/vicious || mutt ||<br />
|-<br />
! [https://github.com/awalGarg/dotfiles awal]<br />
| fish || i3 || vim || sakura || tmux || || i3status || || The Lounge<br />
|-<br />
! [https://github.com/ayekat/dotfiles ayekat]<br />
| zsh || karuiwm || vim || rxvt-unicode || tmux || ncmpcpp/mpd || karuibar || claws-mail/mutt || irssi<br />
|-<br />
! [https://github.com/bamos/dotfiles bamos]<br />
| zsh || i3/xmonad || vim/emacs || rxvt-unicode || tmux || mpv/cmus || conky/xmobar || mutt || ERC<br />
|-<br />
! [https://github.com/pbrisbin/dotfiles brisbin33]<br />
| [https://github.com/pbrisbin/oh-my-zsh zsh] || [https://github.com/pbrisbin/xmonad-config xmonad] || [https://github.com/pbrisbin/vim-config vim] || rxvt-unicode || screen || || dzen || [https://github.com/pbrisbin/mutt-config mutt] || [https://github.com/pbrisbin/irssi-config irssi]<br />
|-<br />
! [https://github.com/bstaletic bstaletic]<br />
| [https://github.com/bstaletic/dotfiles/blob/master/.zshrc zsh] || [https://github.com/bstaletic/dotfiles/blob/master/dwm/config.h dwm] || [https://github.com/bstaletic/dotfiles/blob/master/.vimrc vim]{{Dead link|2016|11|19}} || terminator || screen || [https://github.com/bstaletic/blob/master/.ncmpcpp/config ncmpcpp]{{Dead link|2016|11|19}} || [https://github.com/bstaletic/dotfiles/blob/master/.conkyrc conky] || ||<br />
|-<br />
! [https://github.com/cinelli/dotfiles cinelli]<br />
| zsh || dwm || vim || termite-git || || pianobar || htop || mutt-kz || weechat<br />
|-<br />
! [https://github.com/drkh5h/dotfiles drkhsh]{{Dead link|2017|06|18}}<br />
| zsh || dwm || vim || st || screen || cmus || conky || mutt || weechat<br />
|-<br />
! [https://github.com/Earnestly/dotfiles Earnestly]<br />
| zsh || i3/orbment || vim/emacs || termite || tmux || mpd || conky || mutt || weechat<br />
|-<br />
! [https://github.com/ErikBjare/dotfiles ErikBjare]<br />
| zsh || xmonad/xfce4 || vim || terminator || tmux || || xfce4-panel || || weechat<br />
|-<br />
! [https://github.com/falconindy/dotfiles falconindy]<br />
| bash || i3 || vim || rxvt-unicode || || ncmpcpp || conky || mutt ||<br />
|-<br />
! [https://github.com/graysky2/configs/tree/master/dotfiles graysky]<br />
| zsh || xfce4 || vim || terminal || || ncmpcpp || custom || thunderbird ||<br />
|-<br />
! [http://code.gtmanfred.com/cgit/dotfiles.git/tree/?h=tower gtmanfred]{{Dead link|2016|11|19}}<br />
| zsh || dwm || vim || termite-git || tmux || mpd || conky || mutt || weechat<br />
|-<br />
! [https://github.com/hugdru/dotfiles hugdru]<br />
| zsh || awesome || neovim || rxvt-unicode || tmux || || || thunderbird || weechat<br />
|-<br />
! [https://github.com/insanum/dotfiles insanum]<br />
| bash || herbstluftwm || vim || evilvte || tmux || || dzen || mutt-kz ||<br />
|-<br />
! [https://github.com/izmntuk/archiso/tree/testing/configs/alter/airootfs/ izmntuk]<br />
| zsh || xfce4 || vim || rxvt-unicode/yaft || tmux || cmus || xfce4-panel || || irssi<br />
|-<br />
! [https://bitbucket.org/jasonwryan/shiv/src jasonwryan]<br />
| bash/zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irrsi<br />
|-<br />
! [https://github.com/JDevlieghere/dotfiles/ jdevlieghere]<br />
| zsh || xmonad || vim || terminal || tmux || || htop || mutt || weechat<br />
|-<br />
! [https://github.com/jelly/Dotfiles jelly]<br />
| zsh || i3 || vim || termite || tmux || ncmpcpp || || mutt-kz-git || weechat<br />
|-<br />
! [https://github.com/meskarune/.dotfiles meskarune]<br />
| bash || herbstluftwm || vim || rxvt-unicode || screen || || conky || || weechat<br />
|-<br />
! [https://github.com/neersighted/dotfiles neersighted]<br />
| zsh || i3 || vim || rxvt-unicode || tmux || ncmpcpp || htop || mutt || irssi<br />
|-<br />
! [https://github.com/ok100/configs OK100]<br />
| bash || dwm || vim || rxvt-unicode || || cmus || conky, dzen || mutt || weechat<br />
|-<br />
! [https://github.com/pid1/dotfiles pid1]<br />
| zsh || dwm || neovim || st || tmux || || custom || mutt || weechat<br />
|-<br />
! [https://github.com/polyzen/dotfiles polyzen]<br />
| zsh || i3 || vim || termite || tmux || || i3status || || weechat<br />
|-<br />
! [https://github.com/sistematico/majestic sistematico]<br />
| zsh/fish/bash || [https://github.com/Airblader/i3 i3 Gaps] || vim/nano || termite || tmux || ncmpcpp || i3blocks || mutt || weechat<br />
|-<br />
! [https://github.com/swalladge/dotfiles swalladge]<br />
| zsh/bash || i3 || neovim/vim || termite || tmux || cmus || i3pystatus || mutt ||<br />
|-<br />
! [https://github.com/thiagowfx/dotfiles thiagowfx]<br />
| bash/zsh || i3 || vim/emacs || rxvt-unicode || || ncmpcpp || i3blocks || ||<br />
|-<br />
! [http://hg.subtle.de/dotfiles/file unexist]<br />
| zsh || subtle || vim || rxvt-unicode || || ncmpcpp || || mutt || irssi<br />
|-<br />
! [https://github.com/vodik/dotfiles vodik]<br />
| zsh || xmonad || vim || termite-git || tmux || ncmpcpp || custom || mutt || weechat<br />
|-<br />
! [https://github.com/w0ng/dotfiles w0ng]<br />
| zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irssi<br />
|-<br />
! [https://github.com/Wintervenom/Configuration Wintervenom]<br />
| bash || herbstluftwm ||vim || rxvt-unicode || screen ||mpd ([https://github.com/Wintervenom/Scripts/tree/master/audio/mpd mpc-utils]) || [https://github.com/Wintervenom/Scripts/blob/master/wm/herbstluftwm/hlwm-dzen2 hlwm-dzen2] || mutt || weechat<br />
|-<br />
! [https://github.com/wolfcore/dotfiles wolfcore] <br />
| bash || dwm || vim || rxvt-unicode || tmux || cmus || custom || || weechat<br />
|-<br />
! [https://github.com/xfausto/dotfiles xfausto]{{Dead link|2016|11|19}}<br />
| zsh || dwm || vim || st || || ncmpcpp || conky || ||<br />
|-<br />
! [https://github.com/zendeavor zendeavor]<br />
| [https://github.com/zendeavor/config-stuff/tree/sandbag/zsh zsh] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/config i3] || [https://github.com/zendeavor/dotvim/tree/sandbag vim] || [https://github.com/zendeavor/config-stuff/blob/sandbag/X11/Xresources#L14 rxvt-unicode] || [https://github.com/zendeavor/config-stuff/tree/sandbag/tmux tmux] || [https://github.com/zendeavor/config-stuff/blob/sandbag/ncmpcpp/config ncmpcpp] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/i3status.conf i3status] || || [https://github.com/zendeavor/config-stuff/tree/kiwi/weechat weechat]<br />
|-<br />
! [https://github.com/0n-s/dotfiles dillebidum]<br />
| zsh/mksh || dwm/i3 || vim/vis || st || tmux/dvtm || ncmpcpp/mpv || htop/i3blocks || mutt || ii/irssi<br />
|-<br />
<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[gregswiki:DotFiles]]<br />
* [http://wiki.haskell.org/Xmonad/Config_archive XMonad Config Archive]<br />
* [http://dotshare.it dotshare.it]<br />
* [https://dotfiles.github.io/ dotfiles.github.io]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Dotfiles&diff=490552Dotfiles2017-09-18T03:14:55Z<p>Sistematico: Added sistematico dotfiles</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Dotfiles]]<br />
[[ja:ドットファイル]]<br />
{{Related articles start}}<br />
{{Related|XDG Base Directory support}}<br />
{{Related articles end}}<br />
This article collects user repositories with custom configuration files, commonly known as ''dotfiles''.<br />
<br />
== Version control ==<br />
<br />
Managing dotfiles with version control software such as [[Git]] helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.<br />
<br />
=== Using gitignore ===<br />
<br />
Keeping a [https://git-scm.com/blog/2010/04/11/environment.html git directory] inside the home folder allows to directly keep track of changes. It is recommended to selectively add file contents to the index with {{man|1|git-add}}. <br />
<br />
To prevent untracked files (appearing in commits and removed by {{man|1|git-clean}}), first exclude all files with {{man|5|gitignore}}:<br />
<br />
{{hc|~/.git/info/exclude|<br />
*}}<br />
<br />
Then use {{ic|git add -f}}, for example:<br />
<br />
$ git add -f ~/.config/*<br />
<br />
And commit the changes with {{man|1|git-commit}}:<br />
<br />
$ git commit -a<br />
<br />
=== Other tools ===<br />
<br />
* {{App|dotbot|A minimalist dotfiles manager that can be installed as a git submodule of your dotfiles repository.|https://github.com/anishathalye/dotbot}}<br />
* {{App|dotdrop|A tool to manage different versions of your dotfiles on different hosts.|https://github.com/deadc0de6/dotdrop}}<br />
* {{App|dotfiles|A tool to make managing your dotfile symlinks in $HOME easy, allowing you to keep all of them in a single directory.|https://github.com/jbernard/dotfiles|{{AUR|dotfiles}}}}<br />
* {{App|dotgit|A comprehensive solution to managing your dotfiles.|http://github.com/Cube777/dotgit|{{AUR|dotgit}}}}<br />
* {{App|dots|A portable tool for managing a single set of dotfiles in an organized fashion.|https://github.com/EvanPurkhiser/dots|{{AUR|dots-manager}}}}<br />
* {{App|[[etckeeper]]|Intended to version-control system-wide configuration in /etc. Works by keeping track of permissions and modes which version-control software often ignores. Can use various SCM systems as a backend. Hooks can auto-commit changes to the repository before a system-upgrade.|http://etckeeper.branchable.com/|{{Pkg|etckeeper}}}}<br />
* {{App|GNU Stow|Can be used to symlink dotfiles from a repository into the $HOME tree. See [http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] for more information.|http://www.gnu.org/software/stow/|{{Pkg|stow}}}}<br />
* {{App|homeshick|git dotfiles synchronizer written in bash.|https://github.com/andsens/homeshick|{{AUR|homeshick-git}}}}<br />
* {{App|homesick|Your home directory is your castle. Don't leave your dotfiles behind.|https://github.com/technicalpickles/homesick|{{AUR|homesick}}}}<br />
* {{App|mackup|a small Python utitlity to keep your application settings in sync.|https://github.com/lra/mackup|{{AUR|mackup}}}}<br />
* {{App|Pearl|Package manager for dotfiles, plugins, programs and any form of code accessible via git. Allow to easily share and sync packages across systems and have them ready to work out of the box.|https://github.com/pearl-core/pearl|{{AUR|pearl-git}}}}<br />
* {{App|rcm|Can be used to symlink dotfiles from a repository into the $HOME tree.|https://github.com/thoughtbot/rcm|{{AUR|rcm}}}}<br />
* {{App|vcsh|Allows separating differents modules (e.g., Emacs config vs. zsh config) into individual repositories which can be maintained separately, as opposed to keeping all dotfiles in a single repository. Works with git only.|https://github.com/RichiH/vcsh|{{AUR|vcsh}}}}<br />
* {{App|yadm|Manages files across systems using a single Git repository. Provides a way to use alternate files on a specific OS or host. Supplies a method of encrypting confidential data so it can safely be stored in your repository.|https://github.com/TheLocehiliosan/yadm|{{AUR|yadm-git}}}}<br />
<br />
=== Maintaining dotfiles across multiple machines ===<br />
<br />
{{Style|This and the section below need a rewrite}}<br />
<br />
One way of maintaining dotfiles across various machines across various hosts while still allowing for per-host customizations, is by maintaining a master-branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; as shared configuration is added to the master-branch, the per-machine branches are then rebased on top of the updated master.<br />
<br />
Another approach is to put machine-specific configuration into specially commented blocks and to use [https://pypi.python.org/pypi/mir.qualia/ qualia] to automatically uncomment them on each machine. This approach requires less manual work and doesn't cause merge conflicts.<br />
<br />
=== Confidential information ===<br />
<br />
Occasionally, software may keep plain-text passwords in configuration files, as opposed to hooking into a keyring. In these cases, git clean-filters may be handy to avoid accidentally commiting confidential information. E. g., the following .gitattributes file assigns a filter to the file “some-dotfile”:<br />
<br />
# .gitattributes<br />
some-dotfile filter=remove-pass<br />
<br />
Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in {{ic|.git/config}}, e. g.:<br />
<br />
[filter "remove-pass"]<br />
clean = "sed -e 's/^password=.*/#password=TODO/'"<br />
<br />
== Repositories ==<br />
<br />
{| class="wikitable sortable"<br />
! scope="col" | Author<br />
! scope="col" | Shell (shell framework)<br />
! scope="col" | WM / DE<br />
! scope="col" | Editor<br />
! scope="col" | Terminal<br />
! scope="col" | Multiplexer<br />
! scope="col" | Audio<br />
! scope="col" | Monitor<br />
! scope="col" | Mail<br />
! scope="col" | IRC<br />
|-<br />
! [https://bitbucket.org/ambrevar/dotfiles Ambrevar]<br />
| zsh || awesome || emacs || rxvt-unicode || || cmus || htop/vicious || mutt ||<br />
|-<br />
! [https://github.com/awalGarg/dotfiles awal]<br />
| fish || i3 || vim || sakura || tmux || || i3status || || The Lounge<br />
|-<br />
! [https://github.com/ayekat/dotfiles ayekat]<br />
| zsh || karuiwm || vim || rxvt-unicode || tmux || ncmpcpp/mpd || karuibar || claws-mail/mutt || irssi<br />
|-<br />
! [https://github.com/bamos/dotfiles bamos]<br />
| zsh || i3/xmonad || vim/emacs || rxvt-unicode || tmux || mpv/cmus || conky/xmobar || mutt || ERC<br />
|-<br />
! [https://github.com/pbrisbin/dotfiles brisbin33]<br />
| [https://github.com/pbrisbin/oh-my-zsh zsh] || [https://github.com/pbrisbin/xmonad-config xmonad] || [https://github.com/pbrisbin/vim-config vim] || rxvt-unicode || screen || || dzen || [https://github.com/pbrisbin/mutt-config mutt] || [https://github.com/pbrisbin/irssi-config irssi]<br />
|-<br />
! [https://github.com/bstaletic bstaletic]<br />
| [https://github.com/bstaletic/dotfiles/blob/master/.zshrc zsh] || [https://github.com/bstaletic/dotfiles/blob/master/dwm/config.h dwm] || [https://github.com/bstaletic/dotfiles/blob/master/.vimrc vim]{{Dead link|2016|11|19}} || terminator || screen || [https://github.com/bstaletic/blob/master/.ncmpcpp/config ncmpcpp]{{Dead link|2016|11|19}} || [https://github.com/bstaletic/dotfiles/blob/master/.conkyrc conky] || ||<br />
|-<br />
! [https://github.com/cinelli/dotfiles cinelli]<br />
| zsh || dwm || vim || termite-git || || pianobar || htop || mutt-kz || weechat<br />
|-<br />
! [https://github.com/drkh5h/dotfiles drkhsh]{{Dead link|2017|06|18}}<br />
| zsh || dwm || vim || st || screen || cmus || conky || mutt || weechat<br />
|-<br />
! [https://github.com/Earnestly/dotfiles Earnestly]<br />
| zsh || i3/orbment || vim/emacs || termite || tmux || mpd || conky || mutt || weechat<br />
|-<br />
! [https://github.com/ErikBjare/dotfiles ErikBjare]<br />
| zsh || xmonad/xfce4 || vim || terminator || tmux || || xfce4-panel || || weechat<br />
|-<br />
! [https://github.com/falconindy/dotfiles falconindy]<br />
| bash || i3 || vim || rxvt-unicode || || ncmpcpp || conky || mutt ||<br />
|-<br />
! [https://github.com/graysky2/configs/tree/master/dotfiles graysky]<br />
| zsh || xfce4 || vim || terminal || || ncmpcpp || custom || thunderbird ||<br />
|-<br />
! [http://code.gtmanfred.com/cgit/dotfiles.git/tree/?h=tower gtmanfred]{{Dead link|2016|11|19}}<br />
| zsh || dwm || vim || termite-git || tmux || mpd || conky || mutt || weechat<br />
|-<br />
! [https://github.com/hugdru/dotfiles hugdru]<br />
| zsh || awesome || neovim || rxvt-unicode || tmux || || || thunderbird || weechat<br />
|-<br />
! [https://github.com/insanum/dotfiles insanum]<br />
| bash || herbstluftwm || vim || evilvte || tmux || || dzen || mutt-kz ||<br />
|-<br />
! [https://github.com/izmntuk/archiso/tree/testing/configs/alter/airootfs/ izmntuk]<br />
| zsh || xfce4 || vim || rxvt-unicode/yaft || tmux || cmus || xfce4-panel || || irssi<br />
|-<br />
! [https://bitbucket.org/jasonwryan/shiv/src jasonwryan]<br />
| bash/zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irrsi<br />
|-<br />
! [https://github.com/JDevlieghere/dotfiles/ jdevlieghere]<br />
| zsh || xmonad || vim || terminal || tmux || || htop || mutt || weechat<br />
|-<br />
! [https://github.com/jelly/Dotfiles jelly]<br />
| zsh || i3 || vim || termite || tmux || ncmpcpp || || mutt-kz-git || weechat<br />
|-<br />
! [https://github.com/meskarune/.dotfiles meskarune]<br />
| bash || herbstluftwm || vim || rxvt-unicode || screen || || conky || || weechat<br />
|-<br />
! [https://github.com/neersighted/dotfiles neersighted]<br />
| zsh || i3 || vim || rxvt-unicode || tmux || ncmpcpp || htop || mutt || irssi<br />
|-<br />
! [https://github.com/ok100/configs OK100]<br />
| bash || dwm || vim || rxvt-unicode || || cmus || conky, dzen || mutt || weechat<br />
|-<br />
! [https://github.com/pid1/dotfiles pid1]<br />
| zsh || dwm || neovim || st || tmux || || custom || mutt || weechat<br />
|-<br />
! [https://github.com/polyzen/dotfiles polyzen]<br />
| zsh || i3 || vim || termite || tmux || || i3status || || weechat<br />
|-<br />
! [https://github.com/sistematico/majestic sistematico]<br />
| zsh/fish/bash || i3 || vim/nano || termite || tmux || ncmpcpp || i3blocks || mutt || weechat<br />
|-<br />
! [https://github.com/swalladge/dotfiles swalladge]<br />
| zsh/bash || i3 || neovim/vim || termite || tmux || cmus || i3pystatus || mutt ||<br />
|-<br />
! [https://github.com/thiagowfx/dotfiles thiagowfx]<br />
| bash/zsh || i3 || vim/emacs || rxvt-unicode || || ncmpcpp || i3blocks || ||<br />
|-<br />
! [http://hg.subtle.de/dotfiles/file unexist]<br />
| zsh || subtle || vim || rxvt-unicode || || ncmpcpp || || mutt || irssi<br />
|-<br />
! [https://github.com/vodik/dotfiles vodik]<br />
| zsh || xmonad || vim || termite-git || tmux || ncmpcpp || custom || mutt || weechat<br />
|-<br />
! [https://github.com/w0ng/dotfiles w0ng]<br />
| zsh || dwm || vim || rxvt-unicode || tmux || ncmpcpp || custom || mutt || irssi<br />
|-<br />
! [https://github.com/Wintervenom/Configuration Wintervenom]<br />
| bash || herbstluftwm ||vim || rxvt-unicode || screen ||mpd ([https://github.com/Wintervenom/Scripts/tree/master/audio/mpd mpc-utils]) || [https://github.com/Wintervenom/Scripts/blob/master/wm/herbstluftwm/hlwm-dzen2 hlwm-dzen2] || mutt || weechat<br />
|-<br />
! [https://github.com/wolfcore/dotfiles wolfcore] <br />
| bash || dwm || vim || rxvt-unicode || tmux || cmus || custom || || weechat<br />
|-<br />
! [https://github.com/xfausto/dotfiles xfausto]{{Dead link|2016|11|19}}<br />
| zsh || dwm || vim || st || || ncmpcpp || conky || ||<br />
|-<br />
! [https://github.com/zendeavor zendeavor]<br />
| [https://github.com/zendeavor/config-stuff/tree/sandbag/zsh zsh] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/config i3] || [https://github.com/zendeavor/dotvim/tree/sandbag vim] || [https://github.com/zendeavor/config-stuff/blob/sandbag/X11/Xresources#L14 rxvt-unicode] || [https://github.com/zendeavor/config-stuff/tree/sandbag/tmux tmux] || [https://github.com/zendeavor/config-stuff/blob/sandbag/ncmpcpp/config ncmpcpp] || [https://github.com/zendeavor/config-stuff/blob/sandbag/i3/i3status.conf i3status] || || [https://github.com/zendeavor/config-stuff/tree/kiwi/weechat weechat]<br />
|-<br />
! [https://github.com/0n-s/dotfiles dillebidum]<br />
| zsh/mksh || dwm/i3 || vim/vis || st || tmux/dvtm || ncmpcpp/mpv || htop/i3blocks || mutt || ii/irssi<br />
|-<br />
<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[gregswiki:DotFiles]]<br />
* [http://wiki.haskell.org/Xmonad/Config_archive XMonad Config Archive]<br />
* [http://dotshare.it dotshare.it]<br />
* [https://dotfiles.github.io/ dotfiles.github.io]</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Arch_Linux_(Portugu%C3%AAs)&diff=490220Arch Linux (Português)2017-09-13T17:51:24Z<p>Sistematico: /* Arch Install Scripts not translated */</p>
<hr />
<div>[[Category:About Arch (Português)]]<br />
[[ar:Arch Linux]]<br />
[[bg:Arch Linux]]<br />
[[cs:Arch Linux]]<br />
[[da:Arch Linux]]<br />
[[de:Über Arch Linux]]<br />
[[el:Arch Linux]]<br />
[[en:Arch Linux]]<br />
[[es:Arch Linux]]<br />
[[fi:Arch Linux]]<br />
[[fr:Arch Linux]]<br />
[[he:Arch Linux]]<br />
[[hr:Arch Linux]]<br />
[[hu:Arch Linux]]<br />
[[id:Arch Linux]]<br />
[[it:Arch Linux]]<br />
[[ja:Arch Linux]]<br />
[[ko:Arch Linux]]<br />
[[lt:Arch Linux]]<br />
[[nl:Arch Linux]]<br />
[[pl:Arch Linux]]<br />
[[ro:Arch Linux]]<br />
[[ru:Arch Linux]]<br />
[[sk:Arch Linux]]<br />
[[sr:Arch Linux]]<br />
[[sv:Arch Linux]]<br />
[[th:Arch Linux]]<br />
[[tr:Arch Linux]]<br />
[[uk:Arch Linux]]<br />
[[zh-hans:Arch Linux]]<br />
[[zh-hant:Arch Linux]]<br />
O Arch Linux é uma distribuição GNU/Linux x86_64 de uso geral desenvolvida independentemente que se empenha em fornecer as últimas versões estáveis da maioria dos softwares seguindo um modelo ''rolling-release''. A instalação padrão é um sistema base mínimo, configurado pelo usuário para adicionar apenas o que é propositalmente necessário.<br />
<br />
== Princípios ==<br />
<br />
=== Simplicidade ===<br />
<br />
O Arch Linux define simplicidade como ''sem adições ou modificações desnecessárias''. Ele provê softwares conforme lançado pelos desenvolvedores originais ([[Wikipedia:Upstream (software development)|upstream]]) com alterações mínimas específicas da distribuição (downstream): patches não aceitos pelo upstream são evitados, e patches de downstream do Arch consistem quase totalmente em correções de erros de ''backport'' que são obsoletos pelo próximo lançamento do projeto.<br />
<br />
De uma forma similar, Arch provê os arquivos de configurações fornecidos pelo upstream com alterações limitadas a questões específicas de distribuição, como ajustar caminhos de arquivos de sistema. Ele não adiciona recursos de automação como habilitar um serviço apenas porque o pacote foi instalado. Pacotes só são divididos quando houver vantagens interessantes, tal como economizar espaço em disco em casos em que haja grande desperdício. Utilitários de configuração GUI não são oficialmente fornecidos, incentivando usuários a realizar a maioria da configuração de sistema a partir do shell ou um editor de texto.<br />
<br />
=== Modernidade ===<br />
<br />
O Arch Linux se empenha em oferecer as últimas versões estáveis de seus pacotes desde que quebra sistemática de pacote possa ser razoavelmente evitado. Ele é baseado em um sistema de [[Wikipedia:pt:Rolling release|rolling-release]], que permite uma única instalação e upgrades contínuos.<br />
<br />
O Arch incorpora muitas das mais novas funcionalidades disponíveis para os usuários do GNU/Linux, incluindo o sistema de inicialização [[systemd]], [[file systems|sistemas de arquivos]] modernos, LVM2, RAID via software, suporte ao udev e initcpio (com [[mkinitcpio]]), bem como os últimos kernels.<br />
<br />
=== Pragmatismo ===<br />
<br />
Arch é uma distribuição pragmática, em vez de uma ideológica. Os princípios aqui são apenas diretrizes úteis. Em última análise, decisões de design são feitas caso a caso pelo consenso de desenvolvedores. Análise técnica baseada em evidências e debate são o que importam, não políticas e opinião popular.<br />
<br />
O grande número de pacotes e scripts de compilação nos vários repositórios do Arch Linux oferem software livre e de código aberto para aqueles que o preferem, assim como pacotes de software proprietário para aqueles que adotam funcionalidade sobre ideologia.<br />
<br />
=== Centrado no usuário ===<br />
<br />
Enquanto muitas distribuições GNU/Linux tentam ser mais ''user-friendly'', o Arch Linux sempre foi e sempre será ''user-centric''. O Arch Linux tem a intenção de preencher as necessidades daqueles contribuindo para ele em vez de tentar agradar a maior quantidade de usuários possível. Ele é direcionado para o usuário GNU/Linux avançado ou a qualquer outro com uma atividade "faça você mesmo" que esteja interessado em ler a documentação e resolver seus próprios problemas.<br />
<br />
Todos os usuários são incentivados a [[Getting involved (Português)|participar]] e contribuir com a distribuição. Relatar e ajudar a corrigir [https://bugs.archlinux.org/ falhas] é muito valioso e patches que aprimorem pacotes ou os [https://projects.archlinux.org/ projetos] centrais são muito bem-vindos: desenvolvedores do Arch são voluntários e contribuidores ativos frequentemente se verão se tornando parte da equipe. ''Archers'' podem contribuir livremente com pacotes para o [[Arch User Repository (Português)|Arch User Repository]], melhroar a [[Main page (Português)|documentação do ArchWiki]], fornecer assistência técnica para outros ou apenas trocar opiniões nos [https://bbs.archlinux.org/ fóruns], [https://mailman.archlinux.org/mailman/listinfo/ listas de discussões] ou [[IRC channels|canais IRC]]. Arch Linux é o sistema operacional de escolha para muitos pacotes pelo mundo, e há várias [[international communities|comunidades internacionais]] que oferecem ajuda e fornecem documentação em muitos idiomas diferentes.<br />
<br />
=== Versatilidade ===<br />
<br />
Arch Linux é uma distribuição de propósito geral. Na instalação, apenas um ambiente de linha de comando é fornecido: em vez de separar pacotes desnecessários e indesejados, ao usuário é oferecido a habilidade de compilar um sistema personalizado escolhendo entre milhares de pacotes de alta qualidade fornecidos nos [[repositórios oficiais]] para a arquitetura [[Wikipedia:pt:AMD64|x86-64]]. Suporte para [[Wikipedia:pt:I686|i686]] será [http://www.archlinux-br.org/noticias/254/ cessado] em Novembro de 2017.<br />
<br />
Arch funciona com o [[pacman (Português)|pacman]], um gerenciador de pacotes leve, simples e rápido que permite atualizar todo o sistema com apenas um comando. Arch também fornece o [[Arch Build System (Português)|Arch Build System]], um sistema tipo ''ports'' para facilitar a compilação e instalação de pacotes a partir do fonte, que também pode ser sincronizado com um comando. Além disso, o ''Arch User Repository'' contém muitos milhares mais de scripts [[PKGBUILD (Português)|PKGBUILD]] contribuídos pela comunidade para compilar pacotes instaláveis a partir dos fontes usando o aplicativo [[makepkg (Português)|makepkg]]. Também é possível para usuários compilar e manter seus próprios repositórios personalizados com facilidade.<br />
<br />
== História ==<br />
<br />
=== Os primeiros anos ===<br />
<br />
Judd Vinet, um programador canadense e guitarrista ocasional, começou a desenvolver o Arch Linux no começo de 2001. Seu primeiro lançamento formal, Arch Linux 0.1, foi em 11 de março de 2002. Inspirado pela elegante simplicidade do [http://www.slackware.com/ Slackware], [[wikipedia:pt:Berkeley_Software_Distribution|BSD]], [http://www.pld-linux.org/ PLD Linux] e [http://crux.nu/ CRUX], mas desapontado com a falta de gerenciamento de pacotes na época; Vinet construiu sua própria distribuição com princípios similares àquelas distros; no entanto, ele também escreveu um gerenciador de programas chamado [[pacman (Português)|pacman]], para manipular automaticamente a instalação, remoção e atualizações de pacotes.<br />
<br />
=== Os anos médios ===<br />
<br />
A comunidade inicial do Arch cresceu firmemente, como evidencia [https://dev.archlinux.org/~dan/archstats.svg esse gráfico do número de publicações de fóruns, usuários e relatórios de bugs]. Além disso, foi desde o começo conhecida como [http://www.osnews.com/story/4827 uma comunidade aberta, amigável e prestativa].<br />
<br />
=== Nascimento do ArchWiki ===<br />
<br />
Em 2005-07-08 o ArchWiki foi [[ArchWiki:About (Português)#História|configurado]] pela primeira vez no motor do MediaWiki.<br />
<br />
=== O alvorecer da era A. Griffin ===<br />
<br />
No fim de 2007, Judd Vinet se afastou da participação ativa como desenvolvedor do Arch, e [https://bbs.archlinux.org/viewtopic.php?id=38024 transferiu sem problemas o reinado para o programador americano Aaron Griffin], também conhecido como Phrakture, que continua como líder do desenvolvimento do Arch até hoje.<br />
<br />
Com o passar dos anos, a comunidade do Arch continuou a crescer e amadurecer, e recentemente tem recebido uma quantidade incomum de [[Arch Linux press coverage|atenção e análises]] para uma distro Linux de seu tamanho.<br />
<br />
Os desenvolvedores do Arch continuam a ser voluntários não-pagos e de meio expediente, e não existem expectativas de monetizar o Arch Linux, de modo que ele continuará a ser livre em todos os sentidos da palavra. Aqueles curiosos para ler mais detalhes sobre a história do desenvolvimento do Arch podem navegar na [http://web.archive.org/web/*/archlinux.org entrada sobre o Arch na Internet Archive Wayback Machine].<br />
<br />
=== Scripts de instalação do Arch ===<br />
<br />
O lançamento de 2012-07-15 da imagem de instalação tornou [http://www.archlinux-br.org/noticias/192/ obsoleto] o sistema de menus Arch Installation Framework em favor dos Scripts de Instalação do Arch.<br />
<br />
=== A era do systemd ===<br />
<br />
Entre 2012 e 2013, o tradicional sistema de inicialização System V foi substituído pelo systemd.[http://www.archlinux-br.org/noticias/199/][http://www.archlinux-br.org/noticias/200/][http://www.archlinux-br.org/noticias/204/][http://www.archlinux-br.org/noticias/207/]<br />
<br />
=== Fim do suporte a i686 ===<br />
<br />
Em 2017-01-25, foi [http://www.archlinux-br.org/noticias/254/ anunciado] que o suporte à arquitetura i686 seria encerrado em razão da decrescente popularidade dentre os desenvolvedores e da comunidade.</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Arch_Linux_(Portugu%C3%AAs)&diff=490219Arch Linux (Português)2017-09-13T17:49:25Z<p>Sistematico: /* Versatility is not translated */</p>
<hr />
<div>[[Category:About Arch (Português)]]<br />
[[ar:Arch Linux]]<br />
[[bg:Arch Linux]]<br />
[[cs:Arch Linux]]<br />
[[da:Arch Linux]]<br />
[[de:Über Arch Linux]]<br />
[[el:Arch Linux]]<br />
[[en:Arch Linux]]<br />
[[es:Arch Linux]]<br />
[[fi:Arch Linux]]<br />
[[fr:Arch Linux]]<br />
[[he:Arch Linux]]<br />
[[hr:Arch Linux]]<br />
[[hu:Arch Linux]]<br />
[[id:Arch Linux]]<br />
[[it:Arch Linux]]<br />
[[ja:Arch Linux]]<br />
[[ko:Arch Linux]]<br />
[[lt:Arch Linux]]<br />
[[nl:Arch Linux]]<br />
[[pl:Arch Linux]]<br />
[[ro:Arch Linux]]<br />
[[ru:Arch Linux]]<br />
[[sk:Arch Linux]]<br />
[[sr:Arch Linux]]<br />
[[sv:Arch Linux]]<br />
[[th:Arch Linux]]<br />
[[tr:Arch Linux]]<br />
[[uk:Arch Linux]]<br />
[[zh-hans:Arch Linux]]<br />
[[zh-hant:Arch Linux]]<br />
O Arch Linux é uma distribuição GNU/Linux x86_64 de uso geral desenvolvida independentemente que se empenha em fornecer as últimas versões estáveis da maioria dos softwares seguindo um modelo ''rolling-release''. A instalação padrão é um sistema base mínimo, configurado pelo usuário para adicionar apenas o que é propositalmente necessário.<br />
<br />
== Princípios ==<br />
<br />
=== Simplicidade ===<br />
<br />
O Arch Linux define simplicidade como ''sem adições ou modificações desnecessárias''. Ele provê softwares conforme lançado pelos desenvolvedores originais ([[Wikipedia:Upstream (software development)|upstream]]) com alterações mínimas específicas da distribuição (downstream): patches não aceitos pelo upstream são evitados, e patches de downstream do Arch consistem quase totalmente em correções de erros de ''backport'' que são obsoletos pelo próximo lançamento do projeto.<br />
<br />
De uma forma similar, Arch provê os arquivos de configurações fornecidos pelo upstream com alterações limitadas a questões específicas de distribuição, como ajustar caminhos de arquivos de sistema. Ele não adiciona recursos de automação como habilitar um serviço apenas porque o pacote foi instalado. Pacotes só são divididos quando houver vantagens interessantes, tal como economizar espaço em disco em casos em que haja grande desperdício. Utilitários de configuração GUI não são oficialmente fornecidos, incentivando usuários a realizar a maioria da configuração de sistema a partir do shell ou um editor de texto.<br />
<br />
=== Modernidade ===<br />
<br />
O Arch Linux se empenha em oferecer as últimas versões estáveis de seus pacotes desde que quebra sistemática de pacote possa ser razoavelmente evitado. Ele é baseado em um sistema de [[Wikipedia:pt:Rolling release|rolling-release]], que permite uma única instalação e upgrades contínuos.<br />
<br />
O Arch incorpora muitas das mais novas funcionalidades disponíveis para os usuários do GNU/Linux, incluindo o sistema de inicialização [[systemd]], [[file systems|sistemas de arquivos]] modernos, LVM2, RAID via software, suporte ao udev e initcpio (com [[mkinitcpio]]), bem como os últimos kernels.<br />
<br />
=== Pragmatismo ===<br />
<br />
Arch é uma distribuição pragmática, em vez de uma ideológica. Os princípios aqui são apenas diretrizes úteis. Em última análise, decisões de design são feitas caso a caso pelo consenso de desenvolvedores. Análise técnica baseada em evidências e debate são o que importam, não políticas e opinião popular.<br />
<br />
O grande número de pacotes e scripts de compilação nos vários repositórios do Arch Linux oferem software livre e de código aberto para aqueles que o preferem, assim como pacotes de software proprietário para aqueles que adotam funcionalidade sobre ideologia.<br />
<br />
=== Centrado no usuário ===<br />
<br />
Enquanto muitas distribuições GNU/Linux tentam ser mais ''user-friendly'', o Arch Linux sempre foi e sempre será ''user-centric''. O Arch Linux tem a intenção de preencher as necessidades daqueles contribuindo para ele em vez de tentar agradar a maior quantidade de usuários possível. Ele é direcionado para o usuário GNU/Linux avançado ou a qualquer outro com uma atividade "faça você mesmo" que esteja interessado em ler a documentação e resolver seus próprios problemas.<br />
<br />
Todos os usuários são incentivados a [[Getting involved (Português)|participar]] e contribuir com a distribuição. Relatar e ajudar a corrigir [https://bugs.archlinux.org/ falhas] é muito valioso e patches que aprimorem pacotes ou os [https://projects.archlinux.org/ projetos] centrais são muito bem-vindos: desenvolvedores do Arch são voluntários e contribuidores ativos frequentemente se verão se tornando parte da equipe. ''Archers'' podem contribuir livremente com pacotes para o [[Arch User Repository (Português)|Arch User Repository]], melhroar a [[Main page (Português)|documentação do ArchWiki]], fornecer assistência técnica para outros ou apenas trocar opiniões nos [https://bbs.archlinux.org/ fóruns], [https://mailman.archlinux.org/mailman/listinfo/ listas de discussões] ou [[IRC channels|canais IRC]]. Arch Linux é o sistema operacional de escolha para muitos pacotes pelo mundo, e há várias [[international communities|comunidades internacionais]] que oferecem ajuda e fornecem documentação em muitos idiomas diferentes.<br />
<br />
=== Versatilidade ===<br />
<br />
Arch Linux é uma distribuição de propósito geral. Na instalação, apenas um ambiente de linha de comando é fornecido: em vez de separar pacotes desnecessários e indesejados, ao usuário é oferecido a habilidade de compilar um sistema personalizado escolhendo entre milhares de pacotes de alta qualidade fornecidos nos [[repositórios oficiais]] para a arquitetura [[Wikipedia:pt:AMD64|x86-64]]. Suporte para [[Wikipedia:pt:I686|i686]] será [http://www.archlinux-br.org/noticias/254/ cessado] em Novembro de 2017.<br />
<br />
Arch funciona com o [[pacman (Português)|pacman]], um gerenciador de pacotes leve, simples e rápido que permite atualizar todo o sistema com apenas um comando. Arch também fornece o [[Arch Build System (Português)|Arch Build System]], um sistema tipo ''ports'' para facilitar a compilação e instalação de pacotes a partir do fonte, que também pode ser sincronizado com um comando. Além disso, o ''Arch User Repository'' contém muitos milhares mais de scripts [[PKGBUILD (Português)|PKGBUILD]] contribuídos pela comunidade para compilar pacotes instaláveis a partir dos fontes usando o aplicativo [[makepkg (Português)|makepkg]]. Também é possível para usuários compilar e manter seus próprios repositórios personalizados com facilidade.<br />
<br />
== História ==<br />
<br />
=== Os primeiros anos ===<br />
<br />
Judd Vinet, um programador canadense e guitarrista ocasional, começou a desenvolver o Arch Linux no começo de 2001. Seu primeiro lançamento formal, Arch Linux 0.1, foi em 11 de março de 2002. Inspirado pela elegante simplicidade do [http://www.slackware.com/ Slackware], [[wikipedia:pt:Berkeley_Software_Distribution|BSD]], [http://www.pld-linux.org/ PLD Linux] e [http://crux.nu/ CRUX], mas desapontado com a falta de gerenciamento de pacotes na época; Vinet construiu sua própria distribuição com princípios similares àquelas distros; no entanto, ele também escreveu um gerenciador de programas chamado [[pacman (Português)|pacman]], para manipular automaticamente a instalação, remoção e atualizações de pacotes.<br />
<br />
=== Os anos médios ===<br />
<br />
A comunidade inicial do Arch cresceu firmemente, como evidencia [https://dev.archlinux.org/~dan/archstats.svg esse gráfico do número de publicações de fóruns, usuários e relatórios de bugs]. Além disso, foi desde o começo conhecida como [http://www.osnews.com/story/4827 uma comunidade aberta, amigável e prestativa].<br />
<br />
=== Nascimento do ArchWiki ===<br />
<br />
Em 2005-07-08 o ArchWiki foi [[ArchWiki:About (Português)#História|configurado]] pela primeira vez no motor do MediaWiki.<br />
<br />
=== O alvorecer da era A. Griffin ===<br />
<br />
No fim de 2007, Judd Vinet se afastou da participação ativa como desenvolvedor do Arch, e [https://bbs.archlinux.org/viewtopic.php?id=38024 transferiu sem problemas o reinado para o programador americano Aaron Griffin], também conhecido como Phrakture, que continua como líder do desenvolvimento do Arch até hoje.<br />
<br />
Com o passar dos anos, a comunidade do Arch continuou a crescer e amadurecer, e recentemente tem recebido uma quantidade incomum de [[Arch Linux press coverage|atenção e análises]] para uma distro Linux de seu tamanho.<br />
<br />
Os desenvolvedores do Arch continuam a ser voluntários não-pagos e de meio expediente, e não existem expectativas de monetizar o Arch Linux, de modo que ele continuará a ser livre em todos os sentidos da palavra. Aqueles curiosos para ler mais detalhes sobre a história do desenvolvimento do Arch podem navegar na [http://web.archive.org/web/*/archlinux.org entrada sobre o Arch na Internet Archive Wayback Machine].<br />
<br />
=== Arch Install Scripts ===<br />
<br />
O lançamento de 2012-07-15 da imagem de instalação tornou [http://www.archlinux-br.org/noticias/192/ obsoleto] o sistema de menus Arch Installation Framework em favor do Arch Install Scripts.<br />
<br />
=== A era do systemd ===<br />
<br />
Entre 2012 e 2013, o tradicional sistema de inicialização System V foi substituído pelo systemd.[http://www.archlinux-br.org/noticias/199/][http://www.archlinux-br.org/noticias/200/][http://www.archlinux-br.org/noticias/204/][http://www.archlinux-br.org/noticias/207/]<br />
<br />
=== Fim do suporte a i686 ===<br />
<br />
Em 2017-01-25, foi [http://www.archlinux-br.org/noticias/254/ anunciado] que o suporte à arquitetura i686 seria encerrado em razão da decrescente popularidade dentre os desenvolvedores e da comunidade.</div>Sistematicohttps://wiki.archlinux.org/index.php?title=Table_of_contents_(Portugu%C3%AAs)&diff=70197Table of contents (Português)2009-06-08T14:57:38Z<p>Sistematico: * First change for pt_BR of TOC</p>
<hr />
<div>[[Category:ArchWiki Tools (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|Table of Contents (Česky)}}<br />
{{i18n_entry|Deutsch|Table of Contents (Deutsch)}}<br />
{{i18n_entry|English|Table of Contents (English)}}<br />
{{i18n_entry|Español|Tabla de Contenidos (Español)}}<br />
{{i18n_entry|Français|Table des matières (Français)}}<br />
{{i18n_entry|Italiano|Table of Contents (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Table of Contents (Lietuviškai)}}<br />
{{i18n_entry|Nederlands|Table of Contents (Nederlands)}}<br />
{{i18n_entry|Polski|Table of Contents (Polski)}}<br />
{{i18n_entry|Português do Brasil|Table of Contents (Português do Brasil)}}<br />
{{i18n_entry|Português|Índice de Conteúdos (Português)}}<br />
{{i18n_entry|Русский|Table of Contents (Русский)}}<br />
{{i18n_entry|Română|Table of Contents (Română)}}<br />
{{i18n_entry|Slovensky|Table of Contents (Slovensky)}}<br />
{{i18n_entry|ไทย|Table of Contents (ไทย)}}<br />
{{i18n_entry|Українська|Table of Contents (Українська)}}<br />
{{i18n_entry|简体中文|Table of Contents (简体中文)}}<br />
{{i18n_entry|繁體中文|Table of Contents (繁體中文)}}<br />
{{i18n_entry|正體中文|Table of Contents (正體中文)}}<br />
{{i18n_entry|Ελληνικά|Table of Contents (Ελληνικά)}}<br />
{{i18n_links_end}}<br />
<br />
*[[:Category: About Arch (English)|Sobre o Arch]]<br />
**[[:Category:Events (English)|Eventos]]<br />
*[[:Category: Getting and installing Arch (English)|Baixando e Instalando o Arch]]<br />
*[[:Category: System administration (English)|Administração do sistema]]<br />
**[[:Category:Hardware (English)|Hardware]]<br />
***[[:Category:Arch64 (English)|Arch64]]<br />
***[[:Category:CPU (English)|CPU]]<br />
***[[:Category:Communication and network (English)|Comunicação e rede]]<br />
***[[:Category:Graphics (English)|Gráficos]]<br />
***[[:Category:Hardware detection and troubleshooting (English)|Detecção de hardware e solução de problemas]]<br />
***[[:Category:I586 (English)|I586]]<br />
***[[:Category:Imaging (English)|Imagens]]<br />
***[[:Category:Input devices (English)|Dispositivos de Entrada]]<br />
***[[:Category:Laptops (English)|Laptops]]<br />
***[[:Category:Mainboards and BIOS (English)|Placas-mãe e BIOS]]<br />
***[[:Category:Optical (English)|Dispositivos Óticos]]<br />
***[[:Category:Other hardware (English)|Outro hardware]]<br />
***[[:Category:PowerPC (English)|PowerPC]]<br />
***[[:Category:Printers (English)|Impressoras]]<br />
***[[:Category:Sound (English)|Som]]<br />
***[[:Category:Storage (English)|Armazenamento]]<br />
**[[:Category:Kernel (English)|Kernel]]<br />
**[[:Category:Networking (English)|Rede]]<br />
**[[:Category:Security (English)|Segurança]]<br />
**[[:Category:Software (English)|Software]]<br />
***[[:Category:Boot process (English)|Processo de Inicialização]]<br />
***[[:Category:Command shells (English)|Comandos do shell]]<br />
***[[:Category:Daemons and system services (English)|Daemons e serviços do sistema]]<br />
***[[:Category:Desktop environments (English)|Ambientes Desktop]]<br />
***[[:Category:Display managers (English)|Gerenciadores de tela]]<br />
***[[:Category:Dotfiles (English)|Arquivos-ponto]]<br />
***[[:Category:File systems (English)|Sistemas de arquivo]]<br />
***[[:Category:Fonts (English)|Fontes]]<br />
***[[:Category:Hardware detection and troubleshooting (English)|Hardware e detecção de problemas]]<br />
***[[:Category:Package management (English)|Gerenciamento de pacotes]]<br />
***[[:Category:Power management (English)|Gerenciamento de energia]]<br />
***[[:Category:X Server (English)|Servidor X]]<br />
*[[:Category: Desktop user's guide (English)|Guia do usuário desktop]]<br />
**[[:Category:Audio/Video (English)|Audio/Video]]<br />
**[[:Category:Development (English)|Desenvolvimento]]<br />
**[[:Category:Educational (English)|Educacional]]<br />
**[[:Category:Emulators (English)|Emuladores]]<br />
***[[:Category:Wine (English)|Wine]]<br />
**[[:Category:Eye candy (English)|Aparência]]<br />
**[[:Category:Games and entertainment (English)|Jogos e Entretenimento]]<br />
**[[:Category:Graphics and DTP (English)|Graáficos e DTP]]<br />
**[[:Category:Internationalization (English)|Internacionalização]]<br />
**[[:Category:Internet and Email (English)|Internet e Email]]<br />
**[[:Category:Office (English)|Escritório]]<br />
**[[:Category:Other desktop user's resources (English)|Outros recursos de usuário desktop]]<br />
**[[:Category:Scripts (English)|Scripts]]<br />
**[[:Category:Utilities (English)|Utilidades]]<br />
*[[:Category:System recovery (English)|Recuperação de sistema]]<br />
*[[:Category: Arch development (English)|Desenvolvimento do Arch]]<br />
**[[:Category:Package development (English)|Desenvolvimento de pacotes]]<br />
*[[:Category: Live Arch systems (English)|Sistemas Arch Live]]<br />
*[[:Category:ArchWiki Tools (English)|Ferramentas ArchWiki]]</div>Sistematico