emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [WDYT, mini] key h in agenda for quick help
Date: Wed, 28 Apr 2021 16:08:54 +1000	[thread overview]
Message-ID: <87eeevkka8.fsf@gmail.com> (raw)
In-Reply-To: <87mttj7y74.fsf@bzg.fr>

Bastien <bzg@gnu.org> writes:

> Timothy <tecosaur@gmail.com> writes:
>> Great to hear! I think this would probably be developed as a branch like
>> wip-cite-new
> Yes.
>> , and it would need transient to be installed (via ELPA?) on
>> Emacs <28, but I think it has the potential to both:
>>  - Improve the user experience, and
>>  - Remove Org's own home-cooked transient-ish interfaces,
>>    so leave us with less code to watch over
> Yes, exactly.  Also there is plan to include Transient in Emacs core,
> so this makes this move even more appealing:
> https://lists.gnu.org/archive/html/emacs-devel/2021-04/msg00944.html

I would also suggest that if we were going to have a 'help' key, rather
than describe mode, it might be better to link to the info manual (you
could just link to the agenda section of the manual).

I've rarely found describe mode to be terribly useful (there are
exceptions). However, I have used modes which have bound a help key to a
section in the info manual and I've found that much more useful. The
depth of information is usually better (what people looking for help
probably want) and once your in the info pages, moving to cross
references and other possibly relevant sections is very easy.

I also think adding transient mode would be beneficial in a number of
areas of org. In addition to reducing code maintenance, it would
increase consistency with other Emacs modes etc.

Tim Cross

  reply	other threads:[~2021-04-28  6:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 10:34 [WDYT, mini] key h in agenda for quick help Marco Wahl
2021-02-05 10:55 ` Robert Pluim
2021-02-05 11:55   ` Marco Wahl
2021-02-05 19:48     ` Samuel Wales
2021-02-05 20:25       ` Marco Wahl
2021-02-05 21:02         ` Samuel Wales
2021-04-28  4:17 ` Bastien
2021-04-28  4:59   ` Timothy
2021-04-28  5:06     ` Bastien
2021-04-28  5:36       ` Timothy
2021-04-28  5:52         ` Bastien
2021-04-28  6:08           ` Tim Cross [this message]
2021-04-29 23:15             ` TRS-80
2021-04-29 23:18               ` Samuel Wales
2021-04-30  0:37                 ` Ihor Radchenko
2021-04-28 12:44     ` Greg Minshall
2021-04-28 13:31       ` Timothy
2021-04-28 14:12         ` Greg Minshall
2021-04-29 23:20     ` TRS-80

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eeevkka8.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).