unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Collapse all include lines?
Date: Sun, 15 May 2022 23:41:07 +0200	[thread overview]
Message-ID: <874k1qeaoc.fsf@dataswamp.org> (raw)
In-Reply-To: 878rr2eb73.fsf@dataswamp.org

>>> Is it conceivable to wrap those #include lines by
>>> something like
>>>
>>>   #ifndef DON'T_WANT_TO_SEE
>>>   ...
>>>   #endif
>>
>> I have authority to do that only to files owned by my team.
>> Those are only a tiny fraction of all the files with which
>> I interact. Furthermore, even my own team is likely to
>> resist modifying code merely to cater to my whims :-)
>
> Yeah, plus the very idea to change data to solve an
> interface issue.

Also that's not needed. We can easily recognize such areas
from Elisp.

After that its hidden and replaced with a button; hitting RET
while on that button will show it again will show it while
keeping the button if on would like to close it again.
Gnus does this, for example, with cite regions.

I don't like to do this myself (for source) so can't help you
with the second part (button to hide/show) but that's how/one
way it would/could be done ...

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-05-15 21:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 22:28 Collapse all include lines? John Yates
2022-05-13 22:36 ` Emanuel Berg
2022-05-14  6:21 ` Eli Zaretskii
2022-05-14 20:17   ` John Yates
2022-05-14 21:53     ` Emanuel Berg
2022-05-15  5:13     ` Eli Zaretskii
2022-05-15 14:39       ` Emanuel Berg
2022-05-15 21:05       ` John Yates
2022-05-15 21:29         ` Emanuel Berg
2022-05-15 21:41           ` Emanuel Berg [this message]
2022-05-15 21:07       ` John Yates
2022-05-15 22:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-05-16  0:37   ` Emanuel Berg

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=874k1qeaoc.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@gnu.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).