emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Carlos Pita <carlosjosepita@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: org-toggle-latex-fragment doesn't work as documented [9.2.1 (release_9.2.1-60-gb0379f @ /home/carlos/local/stow/emacs/share/emacs/site-lisp/org/)]
Date: Wed, 13 Feb 2019 11:53:02 -0300	[thread overview]
Message-ID: <CAELgYheXLxshfHJ59kNPgFV=7BxAz-Us7xgoQFAoB13LnKK_bA@mail.gmail.com> (raw)
In-Reply-To: <87a7izu5n4.fsf@nicolasgoaziou.fr>

> WDYT?

I like it. Indeed, I was tempted to suggest removing document scope
but, as an end user, I moderate my proposals to be more or less
conservative.

There are some complications though. If we remove the document scope
bindings we have to refactor the current function quite a bit, because
the interface it provides is purely interactive relying on numerical
arguments. Maybe a split would be in order. I don't like this aspect
that much.

What do you think of this variation of your last proposal:

C-c C-x C-l: as you defined it
C-u C-c C-x C-l: preview document scope.
C-- (or C-0) C-c C-x C-l: as you defined C-u C-c C-x C-l.
C-- (or C-0) C-u C-c C-x C-l: unpreview document scope.

Here I'm keeping both of your bindings although C-u is changed to C--
(or C-0, I think both are good mnemonics - = remove, 0 = leave zero).
Then C-u is free to be used to signal document scope. I dislike the
idea of swapping the roles of this modifiers because of the mnemonic
advantage, even if "clearing previews" is to be used more often than
"document scope".

If you prefer to keep just your two bindings instead, we need to
discuss how to offer the "document scope" interface to the end user.

Best regards
--
Carlos

next prev parent reply	other threads:[~2019-02-13 14:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 22:30 Bug: org-toggle-latex-fragment doesn't work as documented [9.2.1 (release_9.2.1-60-gb0379f @ /home/carlos/local/stow/emacs/share/emacs/site-lisp/org/)] Carlos Pita
2019-02-11 22:33 ` Carlos Pita
2019-02-11 22:51 ` Carlos Pita
2019-02-11 23:15   ` Carlos Pita
2019-02-12 21:45     ` Nicolas Goaziou
2019-02-12 22:00       ` Carlos Pita
2019-02-12 22:43         ` Nicolas Goaziou
2019-02-12 23:23           ` Carlos Pita
2019-02-13 14:25             ` Nicolas Goaziou
2019-02-13 14:53               ` Carlos Pita [this message]
2019-02-13 15:10                 ` Carlos Pita
2019-02-13 16:24                   ` Nicolas Goaziou
2019-02-13 16:43                     ` Carlos Pita
2019-02-13 19:38                       ` Carlos Pita
2019-02-14  0:23                         ` Nicolas Goaziou
2019-02-14  1:31                           ` Carlos Pita
2019-02-14 14:52                             ` 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='CAELgYheXLxshfHJ59kNPgFV=7BxAz-Us7xgoQFAoB13LnKK_bA@mail.gmail.com' \
    --to=carlosjosepita@gmail.com \
    --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

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