unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 29420@debbugs.gnu.org
Subject: bug#29420: 26.0; doc of `list-packages'
Date: Fri, 24 Nov 2017 09:02:46 -0800 (PST)	[thread overview]
Message-ID: <d0fc9fbf-775c-492d-b81d-659c786e59cf@default> (raw)
In-Reply-To: <<838tevafus.fsf@gnu.org>>

> > `C-h f list-packages' should give you a better description of the
> > display that results.  It wouldn't hurt to succinctly describe each
> > column.
> 
> I added the list of columns.

Thanks.

> > `C-h r g package menu' should give you a better description.
> > It should describe each column of the display.
> 
> It does that already.

It does, but the next sentence details the problem
with that description: nothing about `dependency',
for example (dunno whether there are other problems
with the columns description).
 
> > It could describe column `status' better, for instance.  Apparently
> > one of the possible values is `dependency', but that is not
> > mentioned.
> 
> Patches to improve the documentation of package.el in the manual are
> most welcome.  I generally find its documentation inadequate and
> outdated, and tried to improve that as best I could, but I don't know
> enough about it to do a better job, and apparently (and sadly) no one
> else is interested.

I know (and likely care) less about the package system
than you.  Neither of us is well placed, probably, to
help much in this regard.

I do appreciate your attempts to solicit strong doc
along with new developments.  The package system
slipped between the cracks to some extent in this
regard, I guessed.  A guess is that when a large
set of code gets developed outside Emacs first
it can get added to Emacs all at once, and the doc
isn't necessarily gone over with a fine-tooth comb,
in spite of your best efforts.

I agree that it would be great if Someone (TM) gave
the package.el doc some more attention.

> Thanks.

Thank you.






       reply	other threads:[~2017-11-24 17:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<eb6a7e65-28f5-4a3a-86af-c4cca01e0427@default>
     [not found] ` <<838tevafus.fsf@gnu.org>
2017-11-24 17:02   ` Drew Adams [this message]
2017-11-24  2:05 bug#29420: 26.0; doc of `list-packages' Drew Adams
2017-11-24 14:52 ` Eli Zaretskii
2019-10-19  2:04 ` Stefan Kangas
2019-10-19  5:25   ` Drew Adams
2019-10-19  6:42   ` Eli Zaretskii
2019-10-20 15:42     ` Stefan Kangas
2019-10-20 15:58       ` Eli Zaretskii
2019-10-21 23:43         ` Stefan Kangas
2019-10-22 15:20           ` Eli Zaretskii
2019-10-23 14:57             ` Stefan Kangas
2019-10-23 15:47               ` Eli Zaretskii
2019-11-11 14:53                 ` Stefan Kangas
2019-11-14 11:07                   ` Eli Zaretskii
2019-11-15  3:38                     ` Stefan Kangas
2020-01-15  1:27                       ` Stefan Kangas

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=d0fc9fbf-775c-492d-b81d-659c786e59cf@default \
    --to=drew.adams@oracle.com \
    --cc=29420@debbugs.gnu.org \
    --cc=eliz@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).