> Please let me know if anything went wrong.
I think your refactor improves the original code a lot and makes clear
that toggling is just a special case.
I've been testing the changes with a pretty complex beamer document
and found no fault.
Thanks!
Carlos Pita writes:
> Nicolas, here is a patch implementing alternative B above with
> ORG-NEWS entry and everything.
>
> I have been playing with it and find the bindings quite handy.
>
> Code is indeed a bit simpler.
>
> If you like it, feel free to amend it before merging.
Thank you.
I
Nicolas, here is a patch implementing alternative B above with
ORG-NEWS entry and everything.
I have been playing with it and find the bindings quite handy.
Code is indeed a bit simpler.
If you like it, feel free to amend it before merging.
Best regards
--
Carlos
From
> More generally, I feel uneasy about completely hiding stuff. Org format
> is not meant to be opaque. I think the current situation is fine, as far
> as /core/ Org is concerned. Of course, users are free to extend it to
> their own needs.
Yes, indeed.
Occasionally I use
#v+
#+begin_src elisp
I have a column of timestamps and these are more than 24 hours apart and
can't use the ;t format to get durations in a third column when two of
these timestamps are subtracted. Fortunately, I can handle this
application with some basic programming.
--
Hi Michaël,
Michaël Cadilhac writes:
> This is not possible out of the box; can you say a bit more about how
> you expect to indicate which tasks are to be always present?
I would be thinking of something like defining a list of key -> link to
a task (that may be generated with org-id's task
Ok, let's make this more concrete so I can start working on it then.
Alternative A:
Provide three functions:
org-toggle-latex-fragment:
bound to C-c C-x C-l
has an optional argument arg
delegates to org-preview-latex-section if necessary (outside of
fragment or C-u)
Carlos Pita writes:
>> 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.
>
> Btw, I don't think that "preview the entire document" is such a rare
> use
Michaël Cadilhac writes:
> You mention that these drawers don't clutter display, so as an
> example, consider the following screenshot:
> https://michael.cadilhac.name/public/org-props.png
The face you use for drawers is, well obnoxious, to say the least. No
wonder you find them cluttering
On Wed, 13 Feb 2019 at 14:32, Nicolas Goaziou wrote:
> Since properties drawers are almost exclusively folded, I don't think
> incriminated properties clutter display. Besides, I don't think any
> property is irrelevant to every user. How would we know?
I'd have a customizable list of
> 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.
Btw, I don't think that "preview the entire document" is such a rare
use case. Consider that you've
> 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
Hello,
Michaël Cadilhac writes:
> Agreed, hiding properties entirely seems overkill and quite limited in
> use cases. However, I think this stems from a more general need to
> hide properties that are irrelevant to the user—for instance, UIDs
> created by ox-icalendar, or other internal
Hello,
Carlos Pita writes:
> So lets play with minus as a modifier, I like that idea.
>
> (A) Here is a variation of my proposal:
>
> [C- -] [C-u] [C-u] C-c C-x C-l
>
> The modifier [C- -] means force preview.
> The modifier [C-u] means section scope.
> The modifier [C-u][C-u] means document
Hello,
Josiah Schwab writes:
> See discussion at
> https://lists.gnu.org/archive/html/emacs-devel/2019-02/msg00238.html
>
> Sounds like it was fixed in master, but maybe not in maint.
Since the fix is innocuous, I just backported it to maint, too.
Regards,
--
Nicolas Goaziou
See discussion at
https://lists.gnu.org/archive/html/emacs-devel/2019-02/msg00238.html
Sounds like it was fixed in master, but maybe not in maint.
Josiah
I tried to publish a project on Emacs 25.2.1 and received an arithmetic
out of range error on a call to floor. The problem seems to be a call
to floor during the caching process that's out of the 32-bit integer range.
Backtrace follows:
Debugger entered--Lisp error: (range-error "floor"
Hi there Leo;
This is not possible out of the box; can you say a bit more about how
you expect to indicate which tasks are to be always present?
A quick-and-dirty way to implement something along these lines is to
modify org-clock-history-push to always keep a selected set of markers
in
Also, make sure imagemagick is installed.
Btw, you might find this useful for previewing babel-generated images:
(defun my-org-babel-redisplay-images ()
(when org-inline-image-overlays
(org-redisplay-inline-images)))
(add-hook 'org-babel-after-execute-hook
Hi,
> #+HEADER: :file latex.svg
> #+HEADER: :results drawer
> #+BEGIN_SRC latex
I think you're missing some headers to get it working. For example, I
use the following defaults to preview/export images generated with
tikz to html/markdown documents:
Hello,
Carlos Pita writes:
> Not a big deal, but here is a slightly better fix that avoids adding
> some spaces before the closing }.
>
> The difference wrt to the previous one is just:
>
> - (unless (memq (caar tbl) '(:endgroup :endgrouptag)) (insert "\n"))
> - (when (or
Consider this latex source block,
#+HEADER: :file latex.svg
#+HEADER: :results drawer
#+BEGIN_SRC latex
\begin{tikzpicture}
\draw[red] (0,0) circle (1cm);
\end{tikzpicture}
#+END_SRC
I would like to preview the result inline using
Apologies for the spam.
On Wed, Feb 13, 2019 at 9:11 AM Allen Li wrote:
> I don't see an easy good fix due to how Emacs's dynamic variable
> binding works with respect to buffer local variables.
>
> One way to fix is redefine:
>
> (defun org-let (list body)
> (eval `(with-temp-buffer ,(cons
On Wed, Feb 13, 2019 at 8:37 AM Allen Li wrote:
>
> I'm suspicious of org-agenda-mode -> kill-all-local-variables=
>
> One oddity is that repeatedly reverting the buffer swaps between the
> "correct" overriding column format and the default.
It seems like what is happening is that the
On Wed, Feb 13, 2019 at 8:17 AM Allen Li wrote:
>
> 0. Make /tmp/tmp.org containing
>
> * TODO foo bar
>
> 1. emacs -Q
> 2. Eval (setq org-agenda-custom-commands '(("n" "n" alltodo ""
> ((org-agenda-overriding-columns-format "%TODO")
> 3. Eval (setq org-agenda-files '("/tmp/tmp.org"))
> 4.
0. Make /tmp/tmp.org containing
* TODO foo bar
1. emacs -Q
2. Eval (setq org-agenda-custom-commands '(("n" "n" alltodo ""
((org-agenda-overriding-columns-format "%TODO")
3. Eval (setq org-agenda-files '("/tmp/tmp.org"))
4. M-x org-agenda RET n
5. Move point to item
6. C-c C-x C-c (column
26 matches
Mail list logo
