all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman \(gmail\)'" <lennart.borgman@gmail.com>
Cc: 'Tom Tromey' <tromey@redhat.com>, help-gnu-emacs@gnu.org
Subject: RE: Is there any elisp functions to tell whether the cursor is in a	comment block?
Date: Tue, 15 Jul 2008 14:21:25 -0700	[thread overview]
Message-ID: <001c01c8e6c0$bd3203a0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <487D0D8B.7050907@gmail.com>

> >> I am thinking about a page on EmacsWiki that holds the 
> >> information. This page could for example have entries like
> >>
> >>    === Tabkey2.el 21=n 22=y 23=y ===
> >>    elisp:tabkey2.el
> >>    comment ... comment ...
> >>
> >> ELPA could then fetch information from this page. And 
> >> users could too.
> >>
> >> The elisp pages on EmacsWiki could at the bottom have a link 
> >> to this page.
> > 
> > A file-header field in each library file can give the same 
> > information. I use this field, for example:
> > 
> >  ;; Compatibility: GNU Emacs 20.x, GNU Emacs 21.x, GNU Emacs 22.x
> > 
> > However, the field value is free-form at present. A 
> > conventional form would let tools pick up the value.
> > 
> > An advantage is locality of reference and update: some 
> > developers are more likely to update a file header field than
> > a separate wiki page.
> 
> Yes, that might be good too, but it can't be used for packages.

Why not?

If a tool (e.g. ELPA) can pick up the info from a wiki page, as you suggest, why
can't it pick it up from an elisp file (which can also be a wiki page) or a
"package file" or whatever. IOW, whatever info you would provide in the form you
suggested could alternatively be provided in the source code itself. No?





  reply	other threads:[~2008-07-15 21:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13  5:06 Is there any elisp functions to tell whether the cursor is in a comment block? sunway
2008-07-13  9:53 ` Johan Bockgård
2008-07-13 17:55   ` Joe Bloggs
2008-07-13 19:03     ` Johan Bockgård
2008-07-14  1:36       ` Joe Bloggs
2008-07-14  1:49         ` Johan Bockgård
2008-07-14  1:36     ` sunway
2008-07-14 15:05       ` Joe Bloggs
2008-07-14 15:44         ` Lennart Borgman (gmail)
     [not found]         ` <mailman.14707.1216050306.18990.help-gnu-emacs@gnu.org>
2008-07-14 20:10           ` Joe Bloggs
2008-07-14 23:20             ` Lennart Borgman (gmail)
2008-07-14 23:43               ` Drew Adams
2008-07-14 23:49                 ` Lennart Borgman (gmail)
2008-07-15  6:02                   ` Drew Adams
     [not found]                 ` <mailman.14727.1216079418.18990.help-gnu-emacs@gnu.org>
2008-07-15 22:27                   ` David Kastrup
2008-07-20 13:59                 ` Eli Zaretskii
2008-07-15  1:27               ` Tom Tromey
2008-07-15  7:31                 ` Lennart Borgman (gmail)
2008-07-15 14:15                   ` Drew Adams
2008-07-15 20:50                     ` Lennart Borgman (gmail)
2008-07-15 21:21                       ` Drew Adams [this message]
2008-07-15 21:34                         ` Lennart Borgman (gmail)
2008-07-15 22:06                           ` Drew Adams
2008-07-15 22:19                             ` Lennart Borgman (gmail)
2008-07-15 22:32                               ` Drew Adams
2008-07-15 22:47                                 ` Lennart Borgman (gmail)
2008-07-15 22:53                                   ` Drew Adams
     [not found]                             ` <mailman.14800.1216160423.18990.help-gnu-emacs@gnu.org>
2008-07-17 17:40                               ` Giorgos Keramidas
2008-07-17 17:30             ` Giorgos Keramidas
2008-07-19 15:17               ` Joe Bloggs
2008-07-20  0:10                 ` Giorgos Keramidas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001c01c8e6c0$bd3203a0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=tromey@redhat.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.