- Start the editor:
- Open specific files:
xed path/to/file1 path/to/file2 ...
- Open files using a specific encoding:
xed --encoding WINDOWS-1252 path/to/file1 path/to/file2 ...
- Print all supported encodings:
- Open a file and go to a specific line:
xed +10 path/to/file
xed [Options...] [FILES...]
Xed is the official text editor of the X-APPS project, which aims to provide applications to the Cinnamon, MATE and Xfce desktops. While aiming at simplicity and ease of use, Xed is a powerful general purpose text editor. It can be used to create and edit all sorts of text files.
Xed features a flexible plugin system which can be used to dynamically add new advanced features to Xed itself.
This manual page briefly documents the xed command.
Specifies the file to open when xed starts. If this is not specified, xed will start a new, blank file with an "Unsaved Document" label. Multiple files can be loaded if they are separated by spaces. xed also supports handling of remote files.
X display to use.
Set the character encoding to be used for opening the files listed on the command line.
Create a new toplevel window in an existing instance of xed.
Create a new document in an existing instance of xed, on the last Xed window that had focus.
For the first file, go to the line specified by "num" (do not insert a space between the "+" sign and the number). If "num" is missing, go to the last line.
Display list of possible values for the encoding option and exit
Output version information and exit
- -?, -h, --help
Print standard command line options.
- -w, --wait
Open files and block the xed process.
Print all command line options.
This program also accepts the standard GTK options.
xed --encoding WINDOWS-1252 ftp://ftp.kernel.org/pub/linux/kernel/README
Open the Linux Kernel README file from kernel.org's FTP server using Windows-1252 character encoding.
xed +156 http://www.some-website.com/
Open the main web page of some-website.com and jump to line 156.
xed --new-window ~/.bashrc ~/.bash_history
Open the current users .bashrc and .bash_history files in a new window.
Should you encounter any bugs, they may be reported at