From: slists@sezampro.yu
Subject: References to larger comments...
Date: Fri, 21 Nov 2003 16:14:16 +0100 [thread overview]
Message-ID: <1069427656.2296.23.camel@slap> (raw)
Hi,
is there are something like this feature (described below) already in
emacs or some extra lisp packed
or it has to be written.
Feature:
In code comments there are references to a larger comments and if you
execute certain command it is expanded.
Something like in hide-ifdef-mode for ifdefs... Large comments (texts)
would be in different file.
--
example:
original
/* Short comment for everyone... */
/* SOME REFERENCE*/
expended
/* Short comment for everyone...*/
/* Large comment, maybe on another language...
foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo
foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo
foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo */
--
Regards,
reply other threads:[~2003-11-21 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1069427656.2296.23.camel@slap \
--to=slists@sezampro.yu \
/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).