From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 28412@debbugs.gnu.org, kaushal.modi@gmail.com
Subject: bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions
Date: Mon, 18 Sep 2017 22:28:21 +0300 [thread overview]
Message-ID: <831sn3iz6y.fsf@gnu.org> (raw)
In-Reply-To: <87377jizy6.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Mon, 18 Sep 2017 12:12:01 -0700)
> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: Kaushal Modi <kaushal.modi@gmail.com>, 28412@debbugs.gnu.org
> Date: Mon, 18 Sep 2017 12:12:01 -0700
>
> Also, there don't appear to be any built-in functions or regexps for
> dealing with "hidden" buffers, I'm assuming:
>
> (not (string-prefix-p " " (buffer-name buffer)))
>
> is okay?
Yes, but I think aref would be simpler (and probably faster).
prev parent reply other threads:[~2017-09-18 19:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 21:50 bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions Eric Abrahamsen
[not found] ` <handler.28412.B.15050803219580.ack@debbugs.gnu.org>
2017-09-10 22:01 ` bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions) Eric Abrahamsen
2017-09-11 15:03 ` Eli Zaretskii
2017-09-11 21:41 ` Eric Abrahamsen
2017-09-12 14:41 ` Eli Zaretskii
2017-09-12 23:18 ` Eric Abrahamsen
2017-09-18 16:16 ` bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions Kaushal Modi
2017-09-18 18:04 ` Eli Zaretskii
2017-09-18 18:14 ` Eric Abrahamsen
2017-09-18 19:25 ` Eli Zaretskii
2017-09-18 20:30 ` Eric Abrahamsen
2017-09-18 19:12 ` Eric Abrahamsen
2017-09-18 19:23 ` Kaushal Modi
2017-09-18 20:53 ` Eric Abrahamsen
2017-09-18 21:48 ` Kaushal Modi
2017-09-19 16:13 ` Eli Zaretskii
2017-09-25 14:46 ` Kaushal Modi
2017-10-19 15:25 ` Eric Abrahamsen
2017-09-19 16:09 ` Eli Zaretskii
2017-09-18 19:28 ` Eli Zaretskii [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=831sn3iz6y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28412@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=kaushal.modi@gmail.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).