From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: John Yates <john@yates-sheets.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Hide/show support for C++ triple-slash Doxygen markup?
Date: Sat, 29 May 2010 22:00:02 +0200 [thread overview]
Message-ID: <87fx1aa37h.fsf@ambire.localdomain> (raw)
In-Reply-To: <loom.20100529T200426-537@post.gmane.org> (John Yates's message of "Sat, 29 May 2010 18:09:23 +0000 (UTC)")
() John Yates <john@yates-sheets.org>
() Sat, 29 May 2010 18:09:23 +0000 (UTC)
1) block markup comments which are the sole element on the line and may
or may not begin flush left; e.g.
I just tried this in a buffer (copy/paste, M-x c++-mode RET, the latter
makes hideshow commands available under my setup) and they work with
‘hs-toggle-hiding’ on the comment line. The same command in the function
body (between curly braces), does not function in the same way, however.
(It hides from the line following the function name to close curly brace.)
2) trailing markup comments which always follow some number of C++
tokens earlier on the first line but may still spill over onto
subsequent lines; e.g.
I tried this, too, but nothing happened with ‘hs-toggle-hiding’.
Caveat: My hideshow.el and related customizations have probably drifted from
the more widely available (included w/ emacs) versions. Not to mention my
Emacs is from 2008-04-29 and other stick-in-the-mud factors.... YMWUV.
I wonder what hide/show support exists to deal with these conventions.
The most important cases are the block markup comments. Ideally I would
like to be able to eliminate these altogether, meaning that I would
prefer not to waste a line simply to indicate presence of a folded
block markup comment.
You can customize hideshow a bit, perhaps to not adjust the beginning of
the hidden region so much. I'd be interested in hearing how things go.
thi
prev parent reply other threads:[~2010-05-29 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 18:09 Hide/show support for C++ triple-slash Doxygen markup? John Yates
2010-05-29 20:00 ` 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=87fx1aa37h.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=help-gnu-emacs@gnu.org \
--cc=john@yates-sheets.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.
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).