unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Vibhav Pant <vibhavp@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Sivaram Neelakantan <nsivaram.net@gmail.com>
Cc: emacs-devel@gnu.org
Subject: RE: List packages Status column terminology
Date: Fri, 17 Jan 2014 09:39:52 -0800 (PST)	[thread overview]
Message-ID: <5780c0af-a796-4c5d-ba0c-d436ecdf0ec1@default> (raw)
In-Reply-To: <c4119135-bab3-4d3f-9dcd-26d7fc0137d1@email.android.com>

> >Are these field values _links_ that install and uninstall?
>
> No. They are used to indicate whether a package is installed or not.

You cannot uninstall if not installed.  And even if the word "install"
can be interpreted as either update or install from scratch, there
would be no such ambiguity here, since the link "install" would appear
only if the package were not yet installed.

"install" and "uninstall" would let you know unambiguously whether
the package is installed.  Just as clear as "uninstalled" and
"installed", and more useful.

> >If so, "install" and "uninstall" (and "action" instead of "status").
> >If not, why not?
>
> Because packages can be individually installed by clicking on their
> links?

That is not a reason not to provide clear install/uninstall links.
The package-name link is less clear than "install" (even if it might
have a tooltip that clarifies what it does).

Let the link on the package name update, or install if not installed.
Remove that link if the package is already installed.

"install" and "uninstall" links tell you both the status and what
you can do, and they let you do it.


[PS. Why the giant, incomprehensible .sig?  Excusing the brevity
of what you type is not a problem.  What about the non-brevity of
all that PGP .sig crap?]

> - --
> Vibhav Pant
> vibhavp@gmail.com
> 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> -----BEGIN PGP SIGNATURE-----
> Version: APG v1.0.9
> 
> iQI9BAEBCAAnBQJS2VcmIBxWaWJoYXYgUGFudCA8dmliaGF2cEBnbWFpbC5jb20+
> AAoJEO86onTybWtci1EQALY/32Cl2+xXKw3bXtnq0CLhhoYy259Yopzw5Doo4Dzy
> lsosyFfbZvCqxmvLkICat0ItTDAawUokIUk9TcotK7jcygytN1f45vHdOrIqKLui
> i42ZtUB2hNXusRlLLVW3lNymYTbOAjmGBHZuc+EGKiTRd4qW3pfO/B33NDNry/BX
> l3m4yWc1hpNBqeaRXY5Xy5YWFSFZ6L11m0utl6JypgqJ1DI+GaNLz8HxwFEyCjen
> nldP/cw3+z5Hl/bCICKZW4hQoXhDylM2nNQkklsrbpcf5a44DL4ozXevYUyAeqpv
> nh8q9L4d16cHwDfcNd0dIgLItbC7tyXat6c4V6GZO7zw9qqA9GpRJxv33GekGAJE
> +alM/3bZqh5g8jRALx0yielG9qRgcB5/0vG8l7+8uRq0H0pH/QNi/O+VslCyxEWR
> BA+cYwPBxU5wAYSQr2nhEDFUfssHRtO5URwbZgKFty0kDaNnQZeKgXsa6IZIABG3
> yCxF6JU/x5ZBNCU9IAUif48zts3VBvsspyX9nPWzxa1DZvd1EhCrEJlPBdybdALr
> 3H/ifFMCx8oexRza35g10jZ2uRCbMTFTSxNPOeY9YAufl5dJ2ba0YXfTV6BB6iSu
> QG5AicTSM2jAm7dbQpZBlD1y0NQrcIUCVIZw4cThifHbOLTPQuRkM2SpPwziMuLc
> =FF4i
> -----END PGP SIGNATURE-----
> 



  reply	other threads:[~2014-01-17 17:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  4:56 List packages Status column terminology Sivaram Neelakantan
2014-01-17  8:53 ` Thien-Thi Nguyen
2014-01-17 10:19   ` Bozhidar Batsov
2014-01-17 14:17 ` Stefan Monnier
2014-01-17 14:35   ` David Kastrup
2014-01-17 15:12     ` Vibhav Pant
2014-01-17 15:57   ` Drew Adams
2014-01-17 16:15     ` Vibhav Pant
2014-01-17 17:39       ` Drew Adams [this message]
2014-01-17 17:54   ` Sivaram Neelakantan
2014-01-17 21:28     ` Stefan Monnier
2014-01-17 22:55       ` Bozhidar Batsov
2014-01-18  2:44       ` Sivaram Neelakantan
2014-01-19  1:57         ` Stefan Monnier
2014-01-18 12:33   ` Richard Stallman
2014-01-18 12:55     ` Sivaram Neelakantan
2014-01-23 23:38   ` Trent W. Buck
2014-01-24 16:07     ` Stefan Monnier
2014-01-25  1:32       ` Trent W. Buck

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=5780c0af-a796-4c5d-ba0c-d436ecdf0ec1@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nsivaram.net@gmail.com \
    --cc=vibhavp@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).