From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [New exporter] Key bindings and typographical error
Date: Fri, 08 Feb 2013 22:27:02 +0100 [thread overview]
Message-ID: <87a9refqe1.fsf@gmail.com> (raw)
In-Reply-To: <86lib02h3u.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 07 Feb 2013 18:01:25 +0100")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> While using the new dispatcher, I'd like to propose some adaptations -- before
> it's too late (before everybody gets accustomed to your new bindings).
[...]
> In summary:
> - Use "As ... buffer/file" writing
> - Use key `b' for "buffer" result (for both HTML and LaTeX exports)
> - Use only *small* letters for "plain" LaTeX export
> - Use only *capital* letters for "Beamer" LaTeX export
> - Use equivalent capital letters for "plain" -> "Beamer"
As you may have noticed, the current logic for a backend accessed
through a key 'x' is that:
- 'x' will export to a file
- 'X' will export to a temp buffer
Is your proposal really better?
I don't mind changing the bindings for the back-ends (don't forget there
are more than those loaded by default), but I need an incentive to do
so: perfect bindings do not exist, and I don't want to change them every
other day.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-02-08 21:27 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
2013-02-08 21:27 ` Nicolas Goaziou [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9refqe1.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).