From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: master c3ab8f1: Improve buffer-match-p documentation
Date: Sun, 17 Apr 2022 14:30:12 +0300 [thread overview]
Message-ID: <8335icymkb.fsf@gnu.org> (raw)
In-Reply-To: <87lew4f630.fsf@posteo.net> (message from Philip Kaludercic on Sun, 17 Apr 2022 08:48:51 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: emacs-devel@gnu.org
> Date: Sun, 17 Apr 2022 08:48:51 +0000
>
> >> ** New function 'buffer-match-p'
> >> -Check if a buffer matches a condition, specified using a DSL.
> >> +Check if a buffer satisfies some condition. Some examples for
> >> +conditions can be regular expressions that match a buffer name, a
> >> +cons-cell like (major-mode . shell-mode) that matches any buffer where
> >> +major-mode is shell-mode or a combined with a condition like (and
> >> +"\\`\\*.+\\*\\'" (major-mode . special-mode)).
> >
> > Please capitalize "major-mode" and "special-mode", as those stand for
> > something else.
>
> I am not sure I follow you, (major-mode . special-mode) is a condition
> that checks if a buffer derives from `special-mode'. If capitalised, it
> wouldn't do what it should (or rather it would just be ignored).
Sorry, I was confused. Ignore that part.
next prev parent reply other threads:[~2022-04-17 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 8:26 master c3ab8f1: Improve buffer-match-p documentation Eli Zaretskii
2022-04-16 9:53 ` Philip Kaludercic
2022-04-16 11:00 ` Eli Zaretskii
2022-04-16 23:11 ` Philip Kaludercic
2022-04-17 6:42 ` Eli Zaretskii
2022-04-17 8:48 ` Philip Kaludercic
2022-04-17 11:30 ` Eli Zaretskii [this message]
2022-04-17 9:02 ` Philip Kaludercic
2022-04-17 11:31 ` Eli Zaretskii
2022-04-17 12:06 ` Philip Kaludercic
-- strict thread matches above, loose matches on Subject: below --
2022-04-16 8:34 Eli Zaretskii
2022-04-16 8:40 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=8335icymkb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).