all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: "Jose A. Ortega Ruiz" <mail@jao.io>,
	Philip Kaludercic <philipk@posteo.net>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Add 'logos' package
Date: Sat, 12 Mar 2022 09:59:22 +0100	[thread overview]
Message-ID: <87r177tul1.fsf@gmail.com> (raw)
In-Reply-To: <87k0d02wnt.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Fri, 11 Mar 2022 20:04:22 +0200")

Protesilaos Stavrou <info@protesilaos.com> writes:

> If we will still have to explain what the name means, I think it is
> easier to just stick with "logos".  That way I will not have to make any
> changes to the package and my website.

FWIW, I find "logos" to be a fine name for this package.  Might be just
me, but it conveys notions of "speech", "reason", "structured thought",
which IIUC this mode aims at supporting.

The Emacs package ecosystem is no stranger to obscure names that
nonetheless seem to enjoy wide popularity; I'm thinking e.g. of Daniel
Mendler's corfu and vertico.

I think keywords and titles are more suited to solving the problem of
package discovery and visibility.  Trying to stuff as much "relevant"
semantics as possible in the name alone feels counter-productive to me:
finding one or two words that will successfully map to a meaningful
subset of a package's feature, in every user's brain, sounds like a very
hard problem.

IMO this "one-or-two words" budget is better spent on some other purpose
(brevity, catchiness, punniness, theming…).  Again, to me "logos" is
thematically very appropriate.



  reply	other threads:[~2022-03-12  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 10:57 [ELPA] Add 'logos' package Protesilaos Stavrou
2022-03-11 13:22 ` Philip Kaludercic
2022-03-11 13:49   ` Protesilaos Stavrou
2022-03-11 16:02     ` Philip Kaludercic
     [not found] ` <jwvee38y59y.fsf-monnier+emacs@gnu.org>
     [not found]   ` <87y21gbngr.fsf@protesilaos.com>
2022-03-11 13:59     ` Protesilaos Stavrou
2022-03-11 16:16       ` Philip Kaludercic
2022-03-11 16:53         ` Protesilaos Stavrou
2022-03-11 17:15           ` Jose A. Ortega Ruiz
2022-03-11 18:04             ` Protesilaos Stavrou
2022-03-12  8:59               ` Kévin Le Gouguec [this message]
2022-03-12  9:15                 ` Protesilaos Stavrou
2022-03-12  9:22 ` Christopher Dimech

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=87r177tul1.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --cc=mail@jao.io \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.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/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.