From: Robert Eckl <eckl.r@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: [New exporter] Key bindings and typographical error
Date: Sat, 09 Feb 2013 00:38:43 +0100 [thread overview]
Message-ID: <87ehgqbcl8.fsf@sachwertpartner.de> (raw)
In-Reply-To: <86halmu58a.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 08 Feb 2013 17:42:45 +0100")
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Hi Eric,
>
>>
>> and I would also like to take this opportunity to suggest a change in
>> the interface.
>>
>> Given that we have moved to a multi-key sequence for selecting exporter
>> and then action, could these two aspects not be dealt with in the
>> mini-buffer? I find the display of all the options confusing... I
>> would rather have the dispatcher prompt, in the mini-buffer, something
>> along the lines of:
>>
>> : Export to: (l) latex, (h) html, (o) ODT, (a) ascii
>>
>> with the choices obviously depending on the backends initialised. Then,
>> depending on the key (e.g. l):
>>
>> : Export as: (l) file, (b) buffer, (p) PDF, ...
+1
>
> Are you aware of:
>
> (setq org-export-dispatch-use-expert-ui t)
>
> If not, well, you should -- at least from now on!
>
Thanks, i will give that a try
> If yes, then, I guess you mean getting more than just the letters in the echo
> area?
That would be very fine, especially the first days. OTOH i can imagine this is
only "neccesary" for the first steps.
Cu
Robert
next prev parent reply other threads:[~2013-02-08 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 17:01 [New exporter] Key bindings and typographical error Sebastien Vauban
2013-02-08 13:58 ` Eric S Fraga
2013-02-08 14:52 ` Suvayu Ali
2013-02-08 16:52 ` Charles Berry
2013-02-08 23:33 ` Eric S Fraga
2013-02-08 16:42 ` Sebastien Vauban
2013-02-08 23:35 ` Eric S Fraga
2013-02-08 23:38 ` Robert Eckl [this message]
2013-02-08 21:27 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehgqbcl8.fsf@sachwertpartner.de \
--to=eckl.r@gmx.de \
--cc=emacs-orgmode@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/org-mode.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).