Written by ubuntu-user the 23 Jul 10 at 09:33.

if linux user edits configuration files, there are many
fields and values whose purpose needs to be known.
a file editor can help linux user by showing information
on fields, one at a time. this way user does not have to read
man page of the configuration file to edit it. information on
currently active field (field which have cursor on it) is
shown on a separate line dedicated to showing field info.
this could be at the last line of an editor window.
this idea can be applied in any text editor, not just
Emacs.
If there are many lines which belong together, their area
can be highlighted so that user knows they belong together.

if linux user edits configuration files, there are many fields and values whose purpose needs to be known. a file editor can help linux user by showing information on fields, one at a time. this way user does not have to read man page of the configuration file to edit it. information on currently active field (field which have cursor on it) is shown on a separate line dedicated to showing field info. this could be at the last line of an editor window. this idea can be applied in any text editor, not just Emacs. If there are many lines which belong together, their area can be highlighted so that user knows they belong together.

Written by vektor the 25 Jul 10 at 10:12.

Ensure that config files are documented properly via their comments (most of them are already).

This solution renders #1 irrelevant.

Ensure that config files are documented properly via their comments (most of them are already). This solution renders #1 irrelevant.

Written by rockachu2 the 2 Aug 10 at 00:51.

redo directories & document the config files. this wuold make it easy to FIND and EDIT the files.

redo directories & document the config files. this wuold make it easy to FIND and EDIT the files.

Written by samadams the 6 Aug 10 at 01:43.

plain-text config files should go the way of the DoDo bird. XML is perfectly suited to provide robust config preference-list scheme that includes tooltips to show on hover for each preference.

This can easily be facilitated for direct editing via a p-list style editor similar to that used by OS X. Since the file is XML, anyone using a basic text editor can still alter the file directly if desired, including the tool tips and the schema used.

This also facilitates easier designing of GUI interfaces to edit the config file. Standard schema could be defined for certain types of apps or devices, and software vendors can make an easy GUI that interfaces to the p-list file for graphical editing and included with their packages.

Additionally ALL config/preference files should be in the same space in the directory tree, not scattered around with the various software. That, or sym links created all in one space in the tree with the originals residing with the software package for easy cleanup. The sym links should be hard linked so that deleting the original p-list deletes the sym link.

plain-text config files should go the way of the DoDo bird. XML is perfectly suited to provide robust config preference-list scheme that includes tooltips to show on hover for each preference. This can easily be facilitated for direct editing via a p-list style editor similar to that used by OS X. Since the file is XML, anyone using a basic text editor can still alter the file directly if desired, including the tool tips and the schema used. This also facilitates easier designing of GUI interfaces to edit the config file. Standard schema could be defined for certain types of apps or devices, and software vendors can make an easy GUI that interfaces to the p-list file for graphical editing and included with their packages. Additionally ALL config/preference files should be in the same space in the directory tree, not scattered around with the various software. That, or sym links created all in one space in the tree with the originals residing with the software package for easy cleanup. The sym links should be hard linked so that deleting the original p-list deletes the sym link.

Written by earl_maroon the 14 Aug 10 at 02:24.

Encourage a new system in which when a program that has a configuration file is installed, the location of this file, and a description of it, is added to a central configuration file database on your machine, accessible by a simple graphical interface. In this way all files can be easily located and understood.

A backup of the original configuration file should be made automatically.

Encourage a new system in which when a program that has a configuration file is installed, the location of this file, and a description of it, is added to a central configuration file database on your machine, accessible by a simple graphical interface. In this way all files can be easily located and understood. A backup of the original configuration file should be made automatically.

Written by zoubidoo the 3 Jan 11 at 19:51.

Require every config file to have an explicit grammar stored separately. The grammar can be used for parsing, checking for errors, and making user-friendly editing tools. This way, when the config file's grammar changes there is a clear and well-defined change. Also, under a number of circumstances grammar changes will not require changes to applications that use the grammar. All-round it is great for maintainability.

Require every config file to have an explicit grammar stored separately. The grammar can be used for parsing, checking for errors, and making user-friendly editing tools. This way, when the config file's grammar changes there is a clear and well-defined change. Also, under a number of circumstances grammar changes will not require changes to applications that use the grammar. All-round it is great for maintainability.

Written by mzuther the 19 Jul 09 at 11:21.

The current command of "Emacs 22 (client)" already ensures that a file will open in an existing Emacs window if you have an Emacs server running, and will otherwise open a new instance of Emacs. And this is probably the expected behaviour for most users. So just remove the menu entry for "Emacs 22 (GTK)" and rename "Emacs 22 (client)" to "Emacs 22".

The current command of "Emacs 22 (client)" already ensures that a file will open in an existing Emacs window if you have an Emacs server running, and will otherwise open a new instance of Emacs. And this is probably the expected behaviour for most users. So just remove the menu entry for "Emacs 22 (GTK)" and rename "Emacs 22 (client)" to "Emacs 22".

Written by mzuther the 19 Jul 09 at 11:22.

If you want to keep the possibility to open a new instance of Emacs (which one could do from the command line anyway), renaming the menu entries would do most of the trick:

"Emacs 22 (client)" -> "Emacs 22"
"Emacs 22 (GTK)" -> "Emacs 22 (new instance)"

If you want to keep the possibility to open a new instance of Emacs (which one could do from the command line anyway), renaming the menu entries would do most of the trick: "Emacs 22 (client)" -> "Emacs 22" "Emacs 22 (GTK)" -> "Emacs 22 (new instance)"