unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 28412@debbugs.gnu.org
Subject: bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions
Date: Mon, 18 Sep 2017 13:53:24 -0700	[thread overview]
Message-ID: <87vakfenjv.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CAFyQvY3VPmEoWN53qbRc3mHUfz7KPWAFvfcDS30yJs13wpdySQ@mail.gmail.com> (Kaushal Modi's message of "Mon, 18 Sep 2017 19:23:10 +0000")

Kaushal Modi <kaushal.modi@gmail.com> writes:

> On Mon, Sep 18, 2017 at 3:12 PM Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>  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?
>
> That crossed my mind too. So I had started looking for its existing implementation, and found this in buff-menu.el inside list-buffers--refresh function:
>
>     (string= (substring name 0 1) " ")
>
> I was wondering if that should be wrapped into a function like buffer-internal-p (based on the many docstrings like below in buff-menu.el: "By default, the Buffer Menu lists all buffers except those whose names start with a space
> (which are for internal use)."). Having a function like this would be better than having that logic implemented in different ways in the emacs core.
>
> I just don't know the best place to put this function definition. Eli?

It might be nice to have something like:

(defsubst buffer-internal-p (buf)
  (eq (aref (buffer-name buf) 0) ?\s))





  reply	other threads:[~2017-09-18 20:53 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 [this message]
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

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=87vakfenjv.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=28412@debbugs.gnu.org \
    --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).