From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24269@debbugs.gnu.org
Subject: bug#24269: 24.5; Add optional arg to `eval-buffer' and `eval-region' to ignore invisible text
Date: Sat, 27 Jul 2019 09:46:19 -0700 (PDT) [thread overview]
Message-ID: <4ef0b71d-11b6-4d2f-b417-b9a5024635c1@default> (raw)
In-Reply-To: <87blxffrri.fsf@mouse.gnus.org>
> > Enhancement request. Add an optional argument to `eval-buffer' and
> > `eval-region'. When it is non-nil, ignore text that is invisible.
> >
> > More generally, maybe: if a (non-nil) symbol, interpret the symbol as
> a
> > text property, and ignore any text that has a non-nil value of that
> > property.
>
> I don't think that sounds like a clean interface for these functions.
> If you need stuff like this, it sounds like you should just write
> functions that do this for you. Closing.
It's not about me (or anyone) _needing_ this
behavior. It's about the _use cases_ of these
two commands.
It just _makes sense_ for these existing commands
to let you ignore certain zones of text.
They already do that (naturally) for sexps in
comments. Instead of commenting out a zone to
have it ignored, you could well want to eval
only specific zones of text.
That's in fact the _only_ use case of `eval-region':
it ignores text outside the region. Without this
command you would need to narrow the buffer and then
use `eval-buffer'.
Would you argue, using your same logic, that we
should get rid of `eval-region' because you can
always just narrow and use `eval-buffer'?
prev parent reply other threads:[~2019-07-27 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 22:33 bug#24269: 24.5; Add optional arg to `eval-buffer' and `eval-region' to ignore invisible text Drew Adams
2019-07-27 14:58 ` Lars Ingebrigtsen
2019-07-27 16:46 ` Drew Adams [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ef0b71d-11b6-4d2f-b417-b9a5024635c1@default \
--to=drew.adams@oracle.com \
--cc=24269@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.