From: David Kastrup <dak@gnu.org>
Cc: miles@gnu.org
Subject: Re: narrow-to-here-document
Date: 27 Jun 2003 01:10:39 +0200 [thread overview]
Message-ID: <x58yrosads.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20030626.104533.35781860.Takaaki.Ota@am.sony.com>
Tak Ota <Takaaki.Ota@am.sony.com> writes:
> 26 Jun 2003 16:19:57 +0900: Miles Bader <miles@lsi.nec.co.jp> wrote:
>
> > Richard Stallman <rms@gnu.org> writes:
> > > This suggests we should use some other more general term instead.
> > > How about "literal"? Any other suggestions?
> > >
> > > (defun make-indirect-buffer-for-hdoc (&optional change-major-mode)...
> > >
> > > I suggest the name edit-literal for that function.
> > > We should not rigidly put all relevant entities into the function name.
> >
> > I find the name `literal' not clear for the opposite reason -- it seems
> > too broad, and literal seems like a work that might have many other
> > potential meanings. Since the crucial point is that it's a literal field
> > embedded in a buffer, how about something like `edit-embedded-literal' or
> > `edit-literal-field'?
>
> It is a bit pity loosing the name 'here document' since its use is so
> popular that any other naming would be an indirect description of
> 'here document'.
But "here" is a particularly bad keyword for apropos searches. I'd
rather recommend something like "embedded", in particularly since
"here documents" are only a small part of the equation.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-06-26 23:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 13:59 narrow-to-here-document Masatake YAMATO
2003-06-20 14:10 ` narrow-to-here-document Ilya Zakharevich
2003-06-20 16:26 ` narrow-to-here-document Masatake YAMATO
2003-06-21 7:15 ` narrow-to-here-document Stephen J. Turnbull
2003-06-21 8:01 ` narrow-to-here-document David Kastrup
2003-06-21 14:19 ` narrow-to-here-document Ilya Zakharevich
2003-06-21 14:48 ` narrow-to-here-document David Kastrup
2003-06-22 8:33 ` narrow-to-here-document Ilya Zakharevich
2003-06-23 17:10 ` narrow-to-here-document Kevin Rodgers
2003-06-25 6:10 ` narrow-to-here-document Masatake YAMATO
2003-06-25 8:04 ` narrow-to-here-document David Kastrup
2003-06-25 8:21 ` narrow-to-here-document Masatake YAMATO
2003-06-26 0:34 ` narrow-to-here-document Kim F. Storm
2003-06-26 5:30 ` narrow-to-here-document Richard Stallman
2003-06-25 23:18 ` narrow-to-here-document Stefan Daschek
2003-06-26 5:59 ` mmm-mode.el(Re: narrow-to-here-document) Masatake YAMATO
2003-06-26 6:12 ` narrow-to-here-document David Kastrup
2003-06-26 13:00 ` narrow-to-here-document Alan Shutko
2003-06-30 0:34 ` narrow-to-here-document Miles Bader
2003-06-30 6:13 ` narrow-to-here-document Kai Großjohann
2003-06-30 17:19 ` narrow-to-here-document David Kastrup
2003-06-30 20:11 ` narrow-to-here-document Kai Großjohann
2003-07-04 0:07 ` narrow-to-here-document Stefan Monnier
2003-07-04 6:46 ` narrow-to-here-document Kai Großjohann
2003-07-01 15:17 ` narrow-to-here-document Richard Stallman
2003-07-04 0:32 ` narrow-to-here-document Stefan Monnier
2003-07-07 23:45 ` [MMM] narrow-to-here-document Michael A. Shulman
2003-07-08 7:19 ` Kai Großjohann
2003-07-10 16:44 ` Richard Stallman
2003-07-08 14:12 ` mmm-mode needs (was: narrow-to-here-document) Stefan Monnier
2003-07-08 20:02 ` [MMM] Re: narrow-to-here-document Richard Stallman
2003-06-25 16:58 ` narrow-to-here-document Kevin Rodgers
[not found] ` <20030625.143750.116352160.jet@gyve.org>
2003-06-26 5:29 ` narrow-to-here-document Richard Stallman
2003-06-26 7:19 ` narrow-to-here-document Miles Bader
2003-06-26 17:45 ` narrow-to-here-document Tak Ota
2003-06-26 23:10 ` David Kastrup [this message]
2003-06-27 2:07 ` narrow-to-here-document Miles Bader
2003-06-27 2:49 ` narrow-to-here-document Richard Stallman
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=x58yrosads.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=miles@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).