From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Auto-suggesting Packages
Date: Tue, 16 Jan 2024 16:18:01 +0000 [thread overview]
Message-ID: <87a5p59rra.fsf@posteo.net> (raw)
In-Reply-To: <8334uxcnvi.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Jan 2024 17:13:37 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 16 Jan 2024 15:06:02 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Is it really a good idea to show this on the mode line? Why not in
>> > the echo-area? We have several features that suggest tips, and AFAIK
>> > they all show the tips in the echo-area.
>>
>> That is also implemented, I don't know what default is better. The
>> reason I considered the mode line is because having the information
>> displayed persistently might something that newcomer appreciate,
>> especially when they are prone to overlooking something, especially in
>> the echo area.
>
> Then how about displaying it on a header-line instead (or as an
> option)?
>
>> I know that VSCode has something along these lines with
>> a popup window.
>
> We could offer a popup window as well, or (on GUI terminals) maybe a
> dialog box.
Both are possible, but perhaps invasive. The popup buffer that VSCode
displays is more akin to a child window that disappears after a timeout,
and my understanding is that these are a conventional part of the user
experience, which IMO is not the case with Emacs.
prev parent reply other threads:[~2024-01-16 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:18 Auto-suggesting Packages Philip Kaludercic
2024-01-16 9:01 ` Stephen Berman
2024-01-16 9:26 ` Philip Kaludercic
2024-01-16 12:58 ` Eli Zaretskii
2024-01-16 15:06 ` Philip Kaludercic
2024-01-16 15:13 ` Eli Zaretskii
2024-01-16 16:18 ` Philip Kaludercic [this message]
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=87a5p59rra.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).