unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Undocumented hyperlinks in doc strings.
Date: Sat, 18 Oct 2003 20:14:39 -0500 (CDT)	[thread overview]
Message-ID: <200310190114.h9J1EdL03115@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1AB09C-0002ri-3Y@fencepost.gnu.org> (message from Richard Stallman on Sat, 18 Oct 2003 19:06:10 -0400)

Richard Stallman wrote:

   That might be a good solution.  However, users won't all
   remember to do it manually.  Is there a way to make comment-region
   decide this automatically?

Currently, comment-region inserts, by default, in emacs-lisp-mode, two
semicolons and one space at the margin.  With the current convention,
one has to remember to give it a numeric argument of 3 when commenting
out code.  With the proposed new convention, that would only be
necessary when commenting out code _inside_ a function.  Apart from
that the only extra thing to remember would be to leave the extra one
space for the introductory: "this used: " type of sentence, if
present.  I guess it might be feasible to make comment-region insert
three semicolons by default when commenting out code _inside_ a
function with semicolons at the margin (since with two semicolons
C-M-q would mess things up in this situation), but even without that I
believe that comment-region in its present form would interact better
with the new proposed convention that with the current one (because an
explicit numeric argument would be needed less often).

Sincerely,

Luc.

  reply	other threads:[~2003-10-19  1:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  0:50 Undocumented hyperlinks in doc strings Luc Teirlinck
2003-10-09 21:16 ` Richard Stallman
2003-10-10  3:27   ` Luc Teirlinck
2003-10-10 14:14     ` Stefan Monnier
2003-10-10 15:31       ` Luc Teirlinck
2003-10-10 16:29         ` Luc Teirlinck
2003-10-10 17:23         ` Stefan Monnier
2003-10-10 18:21           ` Luc Teirlinck
2003-10-10 19:24             ` Stefan Monnier
2003-10-11 17:12       ` Richard Stallman
2003-10-14 21:03         ` Stefan Monnier
2003-10-15  1:38           ` Luc Teirlinck
2003-10-15 20:00             ` Richard Stallman
2003-10-15 23:52               ` Luc Teirlinck
2003-10-16 23:06                 ` Richard Stallman
2003-10-16 14:06             ` Richard Stallman
2003-10-17  3:32               ` Luc Teirlinck
2003-10-17 13:47                 ` Stefan Monnier
2003-10-18 23:06                   ` Richard Stallman
2003-10-19  1:14                     ` Luc Teirlinck [this message]
2003-10-20  1:48                       ` Richard Stallman
2003-10-20  2:24                         ` Luc Teirlinck
2003-10-20 14:44                           ` Stefan Monnier
2003-10-20 15:22                             ` Luc Teirlinck
2003-10-21 14:47                             ` Richard Stallman
2003-10-11  5:36     ` Richard Stallman
2003-10-12  3:34       ` Luc Teirlinck
2003-10-13  5:03         ` Richard Stallman
2003-10-14  3:23           ` Luc Teirlinck
2003-10-17 20:46             ` Richard Stallman
2003-10-17 23:30               ` Luc Teirlinck

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=200310190114.h9J1EdL03115@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).