unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 7509@debbugs.gnu.org
Subject: bug#7509: 24.0.50; doc for `comment-style' and `comment-styles'
Date: Tue, 30 Nov 2010 17:06:23 -0500	[thread overview]
Message-ID: <jwvk4juv5jf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E61934C52C294DF5A39DCA6F87E1B49E@us.oracle.com> (Drew Adams's message of "Tue, 30 Nov 2010 11:13:03 -0800")

> I came across some variable definition weirdness (unrelated to this
> bug):

I must say I have no idea how you got into such a mess.  My only
explanation would be that some part of the patch did not apply properly.

> Seems there is something buggy about the Customize code or C-M-x or
> both.  C-M-x on a defcustom or a defconst in file foo.el should not
> give a *Help* buffer that says that the var is defined in file bar.el,
> and it should not give the doc from a definition in bar.el.

AFAIK, none of those things occur in my usage.

> What's the magic to competely undo a defcustom or defconst - `makunbound'
> doesn't seem to be enough.

There's no such magic.

> Can you please give me an example of each style, for
> a context/language appropriate to that style?  Then I can try to
> suggest better one-liner descriptions.  If the behavior is different
> depending on whether comment-end is nil, then give me an example of
> each behavior.

From memory: feel free to test them in a C-mode buffer.

plain:

/*      blabla */
/*      bla */

indent

     /* blabla */
     /* bla */
     
multi-line

     /* blabla
      * bla */

extra-line      
      
     /*
      * blabla
      * bla
      */

aligned

     /* blabla */
     /* bla    */
     
box

     /**********/
     /* blabla */
     /* bla    */
     /**********/

box-multi     
     
     /**********
      * blabla *
      * bla    *
      **********/

When comment-end is the empty string,
indent=multi-line=extra-line=aligned and box=box-multi.


        Stefan





  reply	other threads:[~2010-11-30 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 19:42 bug#7509: 24.0.50; doc for `comment-style' and `comment-styles' Drew Adams
2010-11-28 21:01 ` Stefan Monnier
2010-11-28 22:34   ` Drew Adams
2010-11-28 22:49     ` Drew Adams
2010-11-30 18:15       ` Stefan Monnier
2010-11-30 19:13         ` Drew Adams
2010-11-30 22:06           ` Stefan Monnier [this message]
2010-11-30 22:36             ` Drew Adams
2010-12-01  2:57               ` Stefan Monnier
2010-12-01  4:10                 ` Drew Adams
2010-12-03 23:16                   ` Stefan Monnier
2010-12-03 23:34                     ` Drew Adams
2010-11-29  1:38     ` Stefan Monnier

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=jwvk4juv5jf.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=7509@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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).