From: Richard Copley <rcopley@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Lele Gaifax <lele@metapensiero.it>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Nicer confirmation prompt for package.el
Date: Thu, 23 Mar 2017 08:15:29 +0000 [thread overview]
Message-ID: <CAPM58ojiRHZoUczivJw+C=D9-prwE2CbdtrviZ45NCr_YedPEg@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3T9yJ-J_rnYPB=KU11w1wn8Tf=Q1f=Y9xfzM+5i1jX0A@mail.gmail.com>
On 18 March 2017 at 14:11, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>
> On Sat, Mar 18, 2017, 8:52 AM Lele Gaifax <lele@metapensiero.it> wrote:
>>
>> Hi all,
>>
>> when a transaction involves different operations, current
>> `package-menu--prompt-transaction-p' shows prompts like
>>
>> Delete package ‘x’; and Upgrade these 2 packages (y, z)?
>>
>> or
>>
>> Delete package ‘x’; Install package ‘y’; and Upgrade these 2 packages
>> (w, z)?
>>
>> that IMHO are a bit inelegant.
>
>
> I actually like the current message, as the actions Delete, Install and
> Upgrade are capitalized. The user's attention is drawn to the fact that
> those 3 different actions are going to happen. The semi-colons are used so
> that those actions can be capitalized, I think.
That might have been the idea but it's incorrect and looks bad.
A semicolons doesn't end a sentence.
It's not necessary to tell the user what to focus on. The user isn't an idiot :)
[...]
> 1. Current (no change) - Focus on the actions that are going to happen by
> capitalizing them.
> 2. Use of Oxford commas
Perfectly easy to parse the list with or without the serial comma. In my opinion
the comma seems jarring in this case.
I like Lele's suggestion.
prev parent reply other threads:[~2017-03-23 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 12:51 Nicer confirmation prompt for package.el Lele Gaifax
2017-03-18 14:11 ` Kaushal Modi
2017-03-23 8:15 ` Richard Copley [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ojiRHZoUczivJw+C=D9-prwE2CbdtrviZ45NCr_YedPEg@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=lele@metapensiero.it \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.