From: "Paul W. Rankin" via "Emacs development discussions." <emacs-devel@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] lisp/bookmark.el: make bookmark-fontify nil by default
Date: Tue, 18 May 2021 21:08:48 +1000 [thread overview]
Message-ID: <0EA0D44C-0175-4C2F-BFB7-E3187EAC885A@bydasein.com> (raw)
In-Reply-To: <87eee42u69.fsf@tcd.ie>
On 18 May 2021, at 8:49 pm, Basil L. Contovounesios <contovob@tcd.ie> wrote:
>
> The discussion there also raises concerns about some unintended
> consequences of the new feature, such as with Org refile/capture[1] or
> when overwriting an existing bookmark[2].
>
> [1] https://bugs.gnu.org/48179#63
> [2] https://bugs.gnu.org/48179#60
>
> So I suggest you chime in there.
Yep, those are from where I pulled Eli's quote. There's a lot of discussion there but only briefly touching on whether this should be nil by default, where consensus seemed to be nil by default is most appropriate, but then someone yolo'd it to t anyway.
The elephant in the room there that *of course* those with an existing understanding of the feature don't find it disruptive -- they already know exactly what's happening! For everyone else it's a WTF moment (which is now fixed by defaulting to nil; nothing more to see here, move along folks...).
next prev parent reply other threads:[~2021-05-18 11:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 6:20 [PATCH] lisp/bookmark.el: make bookmark-fontify nil by default Paul W. Rankin via Emacs development discussions.
2021-05-18 6:58 ` Karl Fogel
2021-05-18 8:17 ` Paul W. Rankin via Emacs development discussions.
2021-05-18 8:45 ` Eli Zaretskii
2021-05-18 10:06 ` Paul W. Rankin via Emacs development discussions.
2021-05-18 12:09 ` Eli Zaretskii
2021-05-18 12:04 ` Eli Zaretskii
2021-05-18 14:28 ` Lars Ingebrigtsen
2021-05-18 14:38 ` Eli Zaretskii
2021-05-18 14:40 ` Lars Ingebrigtsen
2021-05-19 11:59 ` Bastien
2021-05-19 13:55 ` Eli Zaretskii
2021-05-24 22:32 ` Lars Ingebrigtsen
2021-05-24 22:51 ` [External] : " Drew Adams
2021-05-18 14:43 ` Drew Adams
2021-05-18 15:07 ` Eli Zaretskii
2021-09-13 9:46 ` Stefan Kangas
2021-09-13 9:58 ` Manuel Uberti
2021-09-13 10:17 ` Stefan Kangas
2021-09-13 10:12 ` Colin Baxter
2021-09-13 15:29 ` [External] : " Drew Adams
2021-09-13 10:43 ` Adam Porter
2021-09-13 11:36 ` Lars Ingebrigtsen
2021-09-13 19:36 ` Matthias Meulien
2021-09-14 5:40 ` Colin Baxter
2021-09-14 11:15 ` Lars Ingebrigtsen
2021-09-14 11:46 ` Eli Zaretskii
2021-09-14 11:54 ` Lars Ingebrigtsen
2021-09-14 11:52 ` miha
2021-09-14 11:56 ` Lars Ingebrigtsen
2021-09-14 14:44 ` miha
2021-09-15 7:59 ` Lars Ingebrigtsen
2021-05-18 10:49 ` Basil L. Contovounesios
2021-05-18 11:08 ` Paul W. Rankin via Emacs development discussions. [this message]
2021-05-19 12:00 ` Bastien
2021-05-19 12:58 ` Gregor Zattler
2021-05-18 10:49 ` Basil L. Contovounesios
2021-05-19 12:00 ` Paul W. Rankin via Emacs development discussions.
2021-05-19 14:15 ` 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=0EA0D44C-0175-4C2F-BFB7-E3187EAC885A@bydasein.com \
--to=emacs-devel@gnu.org \
--cc=contovob@tcd.ie \
--cc=pwr@bydasein.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).