From: Daniel Jiang <jngdnl@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>,
Tobias Geerinckx-Rice <me@tobias.gr>,
swedebugia <swedebugia@riseup.net>,
guix-devel@gnu.org
Subject: Re: 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth.
Date: Wed, 27 Mar 2019 13:44:07 -0500 [thread overview]
Message-ID: <CAC9+vAnmVwFKAng7-Tep8CedF-kBJV5irSbUnVaaK2HvQMYhvA@mail.gmail.com> (raw)
In-Reply-To: <87y350fa2e.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 2911 bytes --]
Hello,
Might be related to the subject (?) but would adding something like
keywords/tags to package definitions help? On Emacs, a package definition
like this can pop up:
ack is an available package.
>
> Status: Available from gnu -- Install
> Archive: gnu
> Version: 1.8
> Summary: interface to ack-like tools
> Homepage: https://github.com/leoliu/ack-el
> Keywords: tools processes convenience
>
Then searching packages via keywords can be done:
https://www.gnu.org/software/emacs/manual/html_node/emacs/Package-Keywords.html
On Slackbuilds likewise (keywords somewhere below):
https://slackbuilds.org/repository/14.2/system/guix/
This could be metadata to help find related stuff so there can be a games
tag for the wesnoth package. Also dunno how related, but in Common Lisp
nicknames can be defined for packages. I wrote some game programming
libraries bindings before that uses a longer name for the definition but a
two letter nickname to make it easier to use in practice.
Sincerely,
Daniel Jiang
On Wed, Mar 27, 2019 at 1:26 PM Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
> > TL;DR: we're missing a field like ‘DISPLAY-NAME’, and all this is
> > just hacking around the bush.
>
> This could be a very nice idea!
>
> > Using this logic, I counter that these very long names unfairly
> > privilege 1337 hackers who can touch-type, and hurt the average
> > Jo' poking at their chiclet keyboard with a chopstick ;-)
> >
> > Both arguments make about as much sense IMO (and caricature
> > users). I think a name like ‘the-battle-for-wesnoth’ helps
> > *neither* user.
>
> Users who cannot touch-type will typically perform simple queries, such as:
>
> - battle wesnoth
> - wesnoth battle
> - battle
> - wesnoth
>
> (Using Emacs-Guix.el, Helm, or the next GTK interface.)
>
> With "wesnoth" as a name, 3 out 4 queries won't hit a result.
>
> I don't think that "typing" is the issue here. At least, I wouldn't
> sacrifice the _ability to search_ just to type short names.
>
> Also an option is to alias package names.
>
>
> > XLong names take longer to type on the command line, and noisy to
> > read in code.
>
> Noisy? Why? Short code filled with acronyms tends to be harder to read
> then long explicit names.
>
> Package names are mostly used as inputs. In those longs package lists,
> it's really nice to have explicit names and leave little room for
> ambiguity.
>
> > Some hinder tab-completion.
>
> Why?
>
> > In a GUI, they still look ugly: why no spaces? Why lowercase?
> > Why bother? We don't have to choose between POLA from other
> > command-line package managers and providing pretty metadata for
> > higher-level UIs.
> > We can do both.
>
> Absolutely.
>
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
>
[-- Attachment #2: Type: text/html, Size: 4063 bytes --]
next prev parent reply other threads:[~2019-03-27 18:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190326131842.7363.84034@vcs0.savannah.gnu.org>
[not found] ` <20190326131845.1B177209E3@vcs0.savannah.gnu.org>
2019-03-26 14:54 ` 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server Tobias Geerinckx-Rice
2019-03-26 14:20 ` Pierre Neidhardt
2019-03-26 15:18 ` Ricardo Wurmus
2019-03-26 15:32 ` Pierre Neidhardt
2019-03-26 17:53 ` Andreas Enge
2019-03-26 18:25 ` Pierre Neidhardt
2019-03-27 11:11 ` Ludovic Courtès
2019-03-27 11:36 ` Pierre Neidhardt
[not found] ` <20190326131844.C73EC209E3@vcs0.savannah.gnu.org>
2019-03-27 11:07 ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth Ludovic Courtès
2019-03-27 11:46 ` Pierre Neidhardt
2019-03-27 13:20 ` swedebugia
2019-03-27 15:00 ` Ricardo Wurmus
2019-03-27 16:42 ` Pierre Neidhardt
2019-03-28 7:59 ` Ricardo Wurmus
2019-03-28 8:09 ` Pierre Neidhardt
2019-03-29 13:27 ` swedebugia
2019-03-27 15:15 ` Ludovic Courtès
2019-03-27 18:34 ` Tobias Geerinckx-Rice
2019-03-27 18:26 ` Pierre Neidhardt
2019-03-27 18:44 ` Daniel Jiang [this message]
2019-03-27 21:15 ` Tobias Geerinckx-Rice
2019-03-28 8:17 ` Pierre Neidhardt
2019-03-29 14:02 ` Tobias Geerinckx-Rice
2019-03-29 15:16 ` Andreas Enge
2019-03-29 16:42 ` Naming, hacking, and policies Ludovic Courtès
2019-03-29 19:23 ` Ricardo Wurmus
2019-03-31 16:33 ` Ludovic Courtès
2019-03-30 13:54 ` sirgazil
2019-03-31 16:37 ` Ludovic Courtès
2019-03-31 18:03 ` sirgazil
2019-03-31 20:31 ` Ludovic Courtès
2019-03-31 22:59 ` sirgazil
2019-04-01 0:07 ` Tobias Geerinckx-Rice
2019-03-29 19:57 ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth swedebugia
2019-03-27 15:13 ` Ludovic Courtès
2019-03-27 16:25 ` Pierre Neidhardt
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=CAC9+vAnmVwFKAng7-Tep8CedF-kBJV5irSbUnVaaK2HvQMYhvA@mail.gmail.com \
--to=jngdnl@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=me@tobias.gr \
--cc=swedebugia@riseup.net \
/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/guix.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.