From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: NEWS worthy?
Date: Sat, 08 Mar 2003 05:09:40 -0500 [thread overview]
Message-ID: <E18rbGu-0004i1-00@colo.agora-net.com> (raw)
In-Reply-To: <shk7fa1jnc.fsf@tux.gnu.franken.de> (message from Karl Eichwalder on Sat, 08 Mar 2003 07:01:43 +0100)
From: Karl Eichwalder <keichwa@gmx.net>
Date: Sat, 08 Mar 2003 07:01:43 +0100
I don't know what dcl mode stands for.
DIGITAL (RIP) command language, standard scripting offering under vms.
personal [gt]ripe: at one point i considered myself a budding dcl hacker,
but then a kind soul (at DEC no less) turned me onto emacs, after which
dcl lost its charm due to lack of dcl support in emacs (at the time).
even now, i see the global string font-locking mechanism mishandles
dcl's peculiar (IMHO) quoting conventions; dcl syntax is both over-
and under-permissive in all the wrong places....
> There is no need to put this in NEWS, because users will
> get the benefit of it without having to know about it.
Not necessarily. Maybe, the user has written himself a .dcl mode which
is rather limited. Such a user most probably is interested in the NEWS
of an official dcl mode -- but he will never see it, because he
something as follows in .emacs (like me):
(setq auto-mode-alist
(append
(list
'("\\.dcl$" . dtd-mode)
'("\\.mod$" . dtd-mode))
auto-mode-alist))
the change in question is a minor improvement on the extant dcl-mode,
and so the associated NEWS (had it been worthy) would report this.
reporting existince of dcl-mode happened already w/ emacs 20.1 release.
if a user doesn't read the NEWS that cannot be helped, generally.
thi
prev parent reply other threads:[~2003-03-08 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 23:18 NEWS worthy? Unknown
2003-03-07 2:47 ` John Paul Wallington
2003-03-07 9:01 ` Thien-Thi Nguyen
2003-03-07 19:41 ` Richard Stallman
2003-03-08 2:17 ` Thien-Thi Nguyen
2003-03-08 6:01 ` Karl Eichwalder
2003-03-08 10:09 ` Thien-Thi Nguyen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18rbGu-0004i1-00@colo.agora-net.com \
--to=ttn@glug.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).