From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
Drew Adams <drew.adams@oracle.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Improving describe-mode and discoverability
Date: Thu, 23 Jun 2016 18:27:34 -0400 [thread overview]
Message-ID: <576C6256.6060708@gmail.com> (raw)
In-Reply-To: <9c928ea6-6799-d096-de54-b2bf7ac140ec@yandex.ru>
[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]
On 2016-06-23 18:10, Dmitry Gutov wrote:
> On 06/24/2016 01:07 AM, Drew Adams wrote:
>
>>> Of course, we could put this behaviour behind a flag.
>>
>> If it is a new construct instead of a replacement for \\{...}
>> then there is no need for a flag.
>
> I'd prefer a flag (or just the new behavior). There's no need to split the community here: if I user likes this output, they'll want to see it in all mode descriptions, not just the ones that opted in.
I think I agree. Drew, wouldn't you think that this is something the user should choose, instead of the mode author?
As a user, I'd like consistent rendering; as a mode author, I'd rather not argue with my users about one which one looks best for each one of my modes.
Cheers,
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-06-23 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 18:29 Improving describe-mode and discoverability Clément Pit--Claudel
2016-06-23 18:46 ` Robert Weiner
2016-06-23 18:52 ` Clément Pit--Claudel
2016-06-23 19:11 ` Robert Weiner
2016-06-23 19:36 ` Clément Pit--Claudel
2016-06-23 20:26 ` Drew Adams
2016-06-23 21:50 ` Clément Pit--Claudel
2016-06-23 22:07 ` Drew Adams
2016-06-23 22:10 ` Dmitry Gutov
2016-06-23 22:27 ` Clément Pit--Claudel [this message]
2016-06-23 23:15 ` Drew Adams
2016-06-23 23:39 ` Clément Pit--Claudel
2016-06-24 0:05 ` Drew Adams
2016-06-24 2:59 ` Clément Pit--Claudel
2016-07-06 17:47 ` John Wiegley
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=576C6256.6060708@gmail.com \
--to=clement.pit@gmail.com \
--cc=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
/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).