Manjaro Difference between pages "DMenu" and "Viewing and editing configuration files"

Difference between pages "DMenu" and "Viewing and editing configuration files"

From Manjaro
(Difference between pages)
imported>Stagiros
 
imported>Fhdk
m (→‎Editing files requiring privilege escalation: Added Warning template to GUI sudo edit)
 
Line 1: Line 1:
__TOC__




<br />
=Overview=


Sometimes for no apparent reason users face the following dmenu problem:
= Overview =
<br />
A. When calling dmenu from a key binding in their environment dmenu comes up but when they continue to select anything in dmenu, it disappears from the screen and does not execute anything.
<br />
B. Trying to start dmenu from the terminal, the error <pre>"warning: no locale support"</pre> appears.


In Manjaro, it is common for configuration for the system and applications to reside inside plain text configuration files.  These files can be viewed and edited from both the terminal/tty and from a desktop environment.


=Solution=
= Terminal =


Assuming that you have correctly set up your system's LOCALE settings, here is a simple solution to this problem:
== Viewing configuration files from the terminal/tty ==
<br /><br />
There are two primary ways to view files from the command line.
Edit file /usr/bin/dmenu_run
<pre>sudo nano /usr/bin/dmenu_run</pre>


Add a line setting your LANG variable tou your actual language locale before the line that calls dmenu:
You can use the command cat to dump the contents of a file to the screen by typing cat <filename>.  For example to view the contents of your fstab you could use:
<pre>#!/bin/sh
  cat /etc/fstab
LANG="en_GB.UTF-8"
 
dmenu_path | dmenu "$@" | ${SHELL:-"/bin/sh"} &</pre>
For larger files where it would be better to navigate around you can use less.  For example, to view the contents of your pacman.conf you could type:
and save.
  less /etc/pacman.conf
<br />
 
<br />
== Editing files from the terminal ==
Now dmenu works correctly.
There are many editors available to edit files from the command line but the one that is included with every edition of Manjaro is nano.
 
To open a configuration file with nano simply type nano <filename>.  For example, to edit your .profile file you could type:
  nano ~/.profile
 
The keybindings for nano can be seen at the bottom of the screen.  The ^ indicates the ctrl key.  For example to exit nano you could hold ctrl and press 'x'.
 
Sometimes, escalated privileges are required to edit a file such as most of the files in the /etc directory.  In these cases there are two ways to acquire rights to edit these files.
 
The first is to use sudo to run the text editor.  For example, to edit your fstab file you could type:
  sudo nano /etc/fstab
 
An alternative, and arguably safer method, would be to save a copy of the file somewhere you can write and then use sudo to move it.  For example, if you used nano to edit your fstab and then saved a copy to your home folder, you could then move it to the proper location with sudo:
  sudo mv ~/fstab /etc/fstab
 
= Desktop Environment =
Each Desktop Environment includes a different graphical text editor.  These can be started from the menu/launcher or from the command line.
 
To edit or view a file you can open it directly from the command line.  Reference the list below to find the appropriate editor installed with your edition.  For example to open your pacman.conf from the XFCE edition you could type:
  mousepad /etc/pacman.conf
 
Alternatively, you could launch mousepad from the whisker menu and open the file by browsing to it.  Sometimes, the menu item will have the name as found below but it can also simply read 'Text Editor'
 
== List of graphical text editors for each edition ==
 
* XFCE: mousepad
* Gnome: gedit
* KDE/plasma: kate
* Awesome: mousepad
* bspwn: gedit
* Budgie: gedit
* Cinnamon: xed
* Deepin: gedit
* i3: mousepad
* LXDE: leafpad
* LXQT: juffed-qt5
* MATE: pluma
* Openbox: xed
 
== Editing files requiring privilege escalation ==
Many of the graphical text editors will automatically ask for privilege escalation when they detect that you cannot write to a file.
 
If they don't, you can save a copy of the file to your home folder and move it into place using sudo. For example, if you edit your fstab and then saved a copy to your home folder, you could then move it to the proper location with sudo:
  sudo mv ~/fstab /etc/fstab
 
{{Warning|Never use sudo to run a graphical text editor.  This can have unintended consequences or break the permission to configuration files that should not be owned by root.}}


[[Category:Contents Page]]
[[Category:Contents Page]]

Revision as of 08:51, 16 October 2018


Overview

In Manjaro, it is common for configuration for the system and applications to reside inside plain text configuration files. These files can be viewed and edited from both the terminal/tty and from a desktop environment.

Terminal

Viewing configuration files from the terminal/tty

There are two primary ways to view files from the command line.

You can use the command cat to dump the contents of a file to the screen by typing cat <filename>. For example to view the contents of your fstab you could use:

 cat /etc/fstab

For larger files where it would be better to navigate around you can use less. For example, to view the contents of your pacman.conf you could type:

 less /etc/pacman.conf

Editing files from the terminal

There are many editors available to edit files from the command line but the one that is included with every edition of Manjaro is nano.

To open a configuration file with nano simply type nano <filename>. For example, to edit your .profile file you could type:

 nano ~/.profile

The keybindings for nano can be seen at the bottom of the screen. The ^ indicates the ctrl key. For example to exit nano you could hold ctrl and press 'x'.

Sometimes, escalated privileges are required to edit a file such as most of the files in the /etc directory. In these cases there are two ways to acquire rights to edit these files.

The first is to use sudo to run the text editor. For example, to edit your fstab file you could type:

 sudo nano /etc/fstab

An alternative, and arguably safer method, would be to save a copy of the file somewhere you can write and then use sudo to move it. For example, if you used nano to edit your fstab and then saved a copy to your home folder, you could then move it to the proper location with sudo:

 sudo mv ~/fstab /etc/fstab

Desktop Environment

Each Desktop Environment includes a different graphical text editor. These can be started from the menu/launcher or from the command line.

To edit or view a file you can open it directly from the command line. Reference the list below to find the appropriate editor installed with your edition. For example to open your pacman.conf from the XFCE edition you could type:

 mousepad /etc/pacman.conf

Alternatively, you could launch mousepad from the whisker menu and open the file by browsing to it. Sometimes, the menu item will have the name as found below but it can also simply read 'Text Editor'

List of graphical text editors for each edition

  • XFCE: mousepad
  • Gnome: gedit
  • KDE/plasma: kate
  • Awesome: mousepad
  • bspwn: gedit
  • Budgie: gedit
  • Cinnamon: xed
  • Deepin: gedit
  • i3: mousepad
  • LXDE: leafpad
  • LXQT: juffed-qt5
  • MATE: pluma
  • Openbox: xed

Editing files requiring privilege escalation

Many of the graphical text editors will automatically ask for privilege escalation when they detect that you cannot write to a file.

If they don't, you can save a copy of the file to your home folder and move it into place using sudo. For example, if you edit your fstab and then saved a copy to your home folder, you could then move it to the proper location with sudo:

 sudo mv ~/fstab /etc/fstab


Warning
Never use sudo to run a graphical text editor. This can have unintended consequences or break the permission to configuration files that should not be owned by root.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.