From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: philipk@posteo.net, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: master 50020d026c: Untabify rcirc.el
Date: Thu, 08 Sep 2022 12:36:02 +0300 [thread overview]
Message-ID: <837d2efbst.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmEAUu8QhR+zDnUbPc8qVtvc7e=o7NDUrfN24eha+Uu1g@mail.gmail.com> (message from Stefan Kangas on Thu, 8 Sep 2022 05:07:33 -0400)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 8 Sep 2022 05:07:33 -0400
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
> > It appears to have been added in 2007[0], so this might be viable.
>
> So I guess the below should be uncontroversial?
No, I see no reason for us to impose our preferences on users.
Program switches should not specify anything by default, unless not
doing so makes no sense, or doesn't allow Emacs to communicate with
the program or produce the effect we need.
next prev parent reply other threads:[~2022-09-08 9:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166254232836.24759.17163698181249816742@vcs2.savannah.gnu.org>
[not found] ` <20220907091848.B4E13C04F04@vcs2.savannah.gnu.org>
2022-09-07 11:06 ` master 50020d026c: Untabify rcirc.el Lars Ingebrigtsen
2022-09-07 11:21 ` Philip Kaludercic
2022-09-07 12:11 ` Philip Kaludercic
2022-09-07 21:50 ` Stefan Kangas
2022-09-07 22:07 ` Philip Kaludercic
2022-09-08 9:07 ` Stefan Kangas
2022-09-08 9:20 ` Robert Pluim
2022-09-08 9:39 ` Stefan Kangas
2022-09-08 9:36 ` Eli Zaretskii [this message]
2022-09-08 9:46 ` Stefan Kangas
2022-09-08 10:25 ` Eli Zaretskii
2022-09-08 12:02 ` Robert Pluim
2022-09-08 12:05 ` Philip Kaludercic
2022-09-09 23:13 ` Stefan Kangas
2022-09-08 9:37 ` Philip Kaludercic
2022-09-08 12:04 ` Lars Ingebrigtsen
2022-09-07 12:54 ` Stefan Monnier
2022-09-07 13:22 ` Philip Kaludercic
2022-09-07 11:23 ` Po Lu
2022-09-07 16:42 ` Jim Porter
2022-09-07 18:21 ` 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=837d2efbst.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
--cc=stefankangas@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).