[Pkg-jed-commit] r282 - trunk/packages/jed/debian
Guenter Milde
milde-guest at costa.debian.org
Tue May 16 12:45:59 UTC 2006
Author: milde-guest
Date: 2006-05-16 12:45:58 +0000 (Tue, 16 May 2006)
New Revision: 282
Added:
trunk/packages/jed/debian/NEWS
Modified:
trunk/packages/jed/debian/jed-common.README.Debian
Log:
New file NEWS specifying important changes to the last stable version
(first draft)
jed-common.README.Debian: Describe Debian specific features.
Update the Debian-Jed-FAQ
Added: trunk/packages/jed/debian/NEWS
===================================================================
--- trunk/packages/jed/debian/NEWS 2006-05-16 11:07:20 UTC (rev 281)
+++ trunk/packages/jed/debian/NEWS 2006-05-16 12:45:58 UTC (rev 282)
@@ -0,0 +1,122 @@
+=========================================
+Recent changes to the Debian jed packages
+=========================================
+
+This is a listing of most important changes to the Debian Jed packages
+intended for people upgrading from Sarge (0.99.16-5).
+
+See "changelog.Debian.gz" for a detailled list of Debian specific changes
+and "changelog.gz" for the upstream changes.
+
+
+Packages and contents
+---------------------
+
+* The jed-sl package is dropped. jed-common contains the SLang source of the
+ runtime files. During the installation of jed or xjed the *.sl
+ files will be converted to *.slc files (preparsed).
+
+* new executable jed-script (similar to jed -batch but sets the BATCH
+ variable to 2 and doesnot run the config
+ scripts in /etc/jed.d/)
+
+S-Lang Version 2
+----------------
+
+* Jed now uses S-Lang Version: 2.0.5. There can be incompatibilities
+ breaking home-made or downloaded extensions made for Slang-1.
+
+ New features and upgrade information for version 2 are described in
+ appendix A. "S-Lang 2 Interpreter NEWS" of
+ /usr/share/doc/libslang2/slang.txt.
+
+
+UTF 8 support
+-------------
+
+* Unicode via the UTF-8 encoding is available for jed versions 0.99-17
+ and greater provided that slang2 is used.
+
+ However, this feature is new and still in beta stage but improving. Not
+ all library functions are tested with UTF-8 so expect some "teething
+ problems".
+
+* Enabling UTF-8 support: If the locale indicates that the character set is
+ UTF-8, then UTF-8 mode will be enabled.
+
+ Examples:
+
+ Start xjed in UTF-8 mode: `LANG=de_DE.UTF-8; xjed`
+ Start jed in non-UTF-8 mode: `LANG=de_DE; jed`
+
+ Alias for xjed in UTF-8 mode: alias ujed="LANG=de_DE.UTF-8; xjed"
+
+ (The latter is in my ~/.bashrc.)
+
+ There is no provision for enabling or disabling UTF-8 support during
+ runtime.
+
+ More details under the menu topic
+
+ Help>Browse_Docs utf8
+
+
+Jed_Home_Directory
+------------------
+
+* If the directory "~/.jed/" exists, it will become the `Jed_Home_Directory'
+ and Jed will no longer search for "~/.jedrc" at startup.
+
+ The user needs to move an eventually existing "~/.jedrc" to
+ "~/.jed/jed.rc" ("~/.jed/.jedrc" is still found but deprecated).
+
+* However, Jed will not create such a directory. Users are encouraged to
+ create the directory ".jed/" in their home directory and move an
+ eventually existing ~/.jedrc to ~/.jed/jed.rc (and ~/.jedrecent to
+ ~.jed/.jedrecent).
+
+
+Motivation
+''''''''''
+
+Debian Jed now supports a per-user "~/.jed/" application directory in
+accordance with the file hierarchy standard (FHS 2.3).
+
+ User specific configuration files for applications are stored in the
+ user's home directory in a file that starts with the '.' character (a
+ "dot file"). If an application needs to create more than one dot file
+ then they should be placed in a subdirectory with a name starting with
+ a '.' character, (a "dot directory"). In this case the configuration
+ files should not start with the '.' character.
+
+
+Debian Jed startup scheme
+-------------------------
+
+* The Jed config directory is renamed from "/etc/jed-init.d/" to
+ "/etc/jed.d".
+
+ If there are files in "/etc/jed-init.d/" that are unknown to jed-common,
+ the old directory will remain in place (but not used). The sysadmin should
+ check, manually move remaining files to "/etc/jed.d" and delete
+ "/etc/jed-init.d/".
+
+* The file "/etc/jed.conf" has been removed.
+
+ "/usr/share/jed/lib/defaults.sl" contains the code to evaluate the files
+ in "/etc/jed.d".
+
+ "/etc/jed.d/05jed-common.sl" contains the site-wide configuration of jed
+ (and xjed).
+
+* Evalutation of "/etc/jed.d/" can be suppressed by the
+ --skip-debian-startup command line option.
+
+* "/etc/jed.d/" is not evaluated if Jed is started as `jed-script`.
+
+ If a script depends on the Debian configuration, it can call the function
+ debian_startup() (defined in defaults.sl).
+
+
+For details see README.Debian-startup.
+
Modified: trunk/packages/jed/debian/jed-common.README.Debian
===================================================================
--- trunk/packages/jed/debian/jed-common.README.Debian 2006-05-16 11:07:20 UTC (rev 281)
+++ trunk/packages/jed/debian/jed-common.README.Debian 2006-05-16 12:45:58 UTC (rev 282)
@@ -1,6 +1,74 @@
-Some frequently asked questions:
+============================================================================
+ Readme for the Debian Jed packages
+============================================================================
-Q: When running JED in an xterm, alt is not sending meta (and meta is not
+Jed (http://www.jedsoft.org/jed/) is a highly customizable editor for
+programmers by John E. Davis. Small, fast and mighty. Extensible in the
+C-like S-Lang language.
+
+Jed for debian comes in four packages
+
+ jed console version of Jed
+ xjed stand-alone X application
+ (failsave: falls back to console app if DISPLAY is not set)
+ jed-common Files used by both jed and xjed
+ jed-extra User provided extensions, mainly from http://jedmodes.sf.net/
+
+Jed was debianized by Charl P. Botha and is now maintained by
+the Debian JED Group.
+
+ http://pkg-jed.alioth.debian.org/
+ email: <pkg-jed-devel at lists.alioth.debian.org>
+
+
+Particular features of Debian Jed
+=================================
+
+
+Startup scheme
+--------------
+
+Debian Jed's startup scheme provides for startup code from other packages.
+Instead of a config file, we use a config directory: At startup, Jed will
+evaluate all "*.sl" scripts in /etc/jed.d/. The sysadmin can modify or add
+files in /etc/jed.d/ for site-wide configuration.
+
+See README.Debian-startup for details.
+
+
+Jed_Home_Directory
+------------------
+
+Debian Jed supports a per-user "~/.jed/" application directory in accordance
+with the file hierarchy standard (FHS 2.3). However, Jed will not create
+such a directory. Users are encouraged to create the directory ".jed/" in
+their home directory. It will become the `Jed_Home_Directory'
+where personal jed-related files are assumed to be found, e.g.
+
+ jed.rc user startup configuration (move the jed.rc from the
+ examples/ here and modify to your needs)
+ .jedrecent last opened files (autogenerated by recent.sl)
+ lib/ personal extension scripts (home-made or downloaded)
+ Add to the jed library path in jed.rc with
+
+ set_jed_library_path(path_concat(Jed_Home_Directory, "lib")
+ + "," + get_jed_library_path()
+
+ templates/ optional dir for templates (with jed-extra)
+
+
+ATTENTION: If a user has a "~/.jed/" directory, Jed will not find a
+"~/.jedrc" startup file. The user must move an eventually existing
+"~/.jedrc" to "~/.jed/jed.rc". ("~/.jed/.jedrc" is still found but
+deprecated.)
+
+
+Some frequently asked questions
+-------------------------------
+
+(see also txt/jed_faq.txt.gz)
+
+Q: When running Jed in an xterm, alt is not sending meta (and meta is not
sending escape) so that alt-f and alt-b e.g. don't skip words forwards and
backwards respectively.
A: According to Thomas Dickey (do a google search to see that there is NO
@@ -9,40 +77,64 @@
make sure 'xmodmap -e "keysym Alt_L = Meta_L Alt_L"' is executed
somewhere at X-startup (modify e.g. ~/.Xmodmap).
-Q: When I paste text into JED, it misaligns everything (i.e. every succeeding
+Q: When I paste text into Jed, it misaligns everything (i.e. every succeeding
line is indented more than the previous, yielding horizontally cascading
- text). How can I prevent this?
-A1: Use the paste_mode that John E. Davis has supplied. See the start of
- /usr/share/jed/lib/paste_mode.sl for instructions.
-A2: In JED, carriage return is bound to newline_and_indent. You can
- temporarily change this by doing:
- 1. M-x no_mode
- 2. M-x evaluate-cmd
- 3. setkey("newline","^M") (at the S-Lang prompt)
- 4. Now paste your text...
- 5. M-x evaluate-cmd
- 6. setkey("newline_and_indent","^M") (at the S-Lang prompt)
- 7. now go back to whichever editing mode you were in, e.g. M-x c_mode
-
+ text).
+A: In Jed, carriage return is bound to `newline_and_indent'. While this
+ auto-indention is a great help in normal editing, it stands in the way
+ when text is pasted via the mouse. Unfortunately, Jed cannot tell whether
+ its input comes from a keyboard, another program, or the mouse (XJed can).
+
+Q: How can I prevent this?
+A0: Use xjed.
+A1: Use the `paste' function
+ 1. M-x paste (or bind "paste" to a key)
+ 2. Now paste your text...
+A2: Temporarily change the keybinding by doing:
+ 1. M-X local_setkey("newline","^M") (Alt-Shift-X: the S-Lang prompt)
+ 3. Now paste your text...
+ 4. M-X local setkey("newline_and_indent","^M")
+A3: Bind "newline_and_indent" to a different key. In jed.rc do e.g.:
+ setkey("newline_and_indent", "\e^M"); % Key_Alt_Return
+ setkey("newline", "^M");
+A4: Use the fact that Jed can tell whether there is input pending after the
+ carriage return. Define in your jed.rc (or any other file evaluated at
+ startup):
+ public define newline_indent ()
+ {
+ if (input_pending(0))
+ newline();
+ else
+ call ("newline_and_indent");
+ }
+ setkey("newline_indent","^M");
+ On a slow terminal (remote login or heavy load) this might fail by
+ non-indenting after fast typing of CR and the first character of the new
+ line.
+
Q: TAB does not generate a TAB! Why?
A: Please see /usr/share/doc/jed-common/jed_faq.txt.gz, question #13.
-Q: I expected JED to make a difference between a single '/' and multible '/'
- in pathnames - e.g. '/usr//bin/' is *not* equal to '/usr/bin/' ! Why ?
-A: According to John E. Davis, the author, this is like Emacs behave, too.
+Q: I expected Jed to make a difference between a single '/' and multiple '/'
+ in pathnames - e.g. '/usr//bin/' is *not* equal to '/usr/bin/' ! Why?
+A: According to John E. Davis, the author, this is like Emacs behaves, too.
Q: I have a colour scheme which does NOT modify the background and
- foreground colours, yet JED is still changing this, thus overriding the
+ foreground colours, yet Jed is still changing this, thus overriding the
default colours of the terminal it's running in. What's wrong?
A: If you're only using set_color() calls but never call set_color_scheme(),
- JED automatically calls set_color_scheme() on _Jed_Default_Color_Scheme.
- So, to fix your problem, put "_Jed_Default_Color_Scheme = NULL;" in
- your ~/.jedrc.
+ Jed automatically calls set_color_scheme() with the
+ _Jed_Default_Color_Scheme. So, to fix your problem, put
+ "_Jed_Default_Color_Scheme = NULL;" in your ~/.jedrc.
-Q: Why is jed linked against the libncurses when it uses slang ?
-A: Because it has GPM mouse support and these libraries needs ncurses.
+Q: Why is jed linked against libncurses when it uses slang?
+A: Because it has GPM mouse support and these libraries need ncurses.
-Q: The configuration files seem somewhat confusing to me. Can you explain ?
+Q: The configuration files seem somewhat confusing to me. Can you explain?
A: See /usr/share/doc/jed-common/README.Debian-startup
+.. Copyright (c) 2006 the Debian JED Group
+ Released under the terms of the GNU General Public License (ver. 2 or later)
+
+ Last update 2006-05-16 Guenter Milde
More information about the Pkg-jed-commit
mailing list