From: "Jose A. Ortega Ruiz" <mail@jao.io>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Add 'logos' package
Date: Fri, 11 Mar 2022 17:15:31 +0000 [thread overview]
Message-ID: <87fsnotnpo.fsf@gnus.jao.io> (raw)
In-Reply-To: <87sfro2zxs.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Fri, 11 Mar 2022 18:53:35 +0200")
On Fri, Mar 11 2022, Protesilaos Stavrou wrote:
[...]
> I had thought about something pertaining to presentations but discarded
> it. It felt like it was emphasising one use-case, whereas the package
> can be used simply to read or write or just as a convenience for moving
> around the buffer. Same principle for anything that hinted at "focus".
>
> Again, I am open to suggestions. Though I have ran out of ideas. Hence
> the generic name I chose.
I haven't fully followed this thread, so apologies if these have already
been mentioned: "locus" sounds pretty suggestive to me, and i also quite
like the more daring "limelight".
Cheers,
jao
--
One reason that life is complex is that it has a real part and an
imaginary part.
-Andrew Koenig
next prev parent reply other threads:[~2022-03-11 17:15 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 [this message]
2022-03-11 18:04 ` Protesilaos Stavrou
2022-03-12 8:59 ` Kévin Le Gouguec
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=87fsnotnpo.fsf@gnus.jao.io \
--to=mail@jao.io \
--cc=emacs-devel@gnu.org \
--cc=info@protesilaos.com \
--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.