Re: [O] Export to multiple HTML files
This: https://github.com/mbork/org-one-to-many may be a starting point. It is a small library which splits an org file into many smaller ones. (Bug reports/feature requests welcome, btw.) The main function returns the list of generated files, so you could #'mapc some export function over it. Thanks! I'll check this out. It makes it a lot easier for another project I'm working on involving Gopher, too.
[O] Filter by tags issues
I'm having an annoying issue with filter by tag. I filter everything that has @computer, process one item and send it to the archive file; as soon as I archive it, the next item on the list pops up - this item might be a @home item. How do I stop this from happening? Thanks.
[O] refiling with helm
Hi guys I was wondering if anyone uses helm for refiling org capture data. and if so can anyone share his methods/setup? googling for it didnt yield to many results (especially for people like me who dont know to code :)) thx Z
[O] Sorting CLOCK entries
Hello there, I was wondering if there is a way to sort clock entries like in the clock entries below. The table is sorted in reverse chronological order except for the last two. I was wondering if there is some to sort these entries so that the last two entries sit in the right place. CLOCK: [2015-01-21 Wed 16:37]--[2015-01-21 Wed 16:53] = 0:16 CLOCK: [2014-12-02 Tue 18:29]--[2014-12-02 Tue 18:57] = 0:28 CLOCK: [2014-12-02 Tue 11:50]--[2014-12-02 Tue 12:01] = 0:11 CLOCK: [2014-12-01 Mon 17:32]--[2014-12-01 Mon 17:57] = 0:25 CLOCK: [2014-10-27 Mon 17:10]--[2014-10-27 Mon 17:47] = 0:37 CLOCK: [2014-10-24 Fri 11:17]--[2014-10-24 Fri 11:24] = 0:07 CLOCK: [2014-10-30 Thu 11:22]--[2014-10-30 Thu 11:43] = 0:21 CLOCK: [2014-10-29 Wed 13:22]--[2014-10-29 Wed 13:37] = 0:15 CLOCK: [2014-10-29 Wed 12:05]--[2014-10-29 Wed 12:10] = 0:05 CLOCK: [2014-10-21 Tue 20:13]--[2014-10-21 Tue 20:31] = 0:18 CLOCK: [2014-10-21 Tue 19:03]--[2014-10-21 Tue 19:45] = 0:42 CLOCK: [2014-10-21 Tue 18:27]--[2014-10-21 Tue 18:32] = 0:05 CLOCK: [2014-10-21 Tue 11:33]--[2014-10-21 Tue 11:34] = 0:01 CLOCK: [2014-10-20 Mon 15:05]--[2014-10-20 Mon 15:37] = 0:32 CLOCK: [2014-10-20 Mon 11:55]--[2014-10-20 Mon 12:01] = 0:06 CLOCK: [2014-10-20 Mon 11:07]--[2014-10-20 Mon 11:53] = 0:46 CLOCK: [2014-10-17 Fri 15:43]--[2014-10-17 Fri 15:57] = 0:14 CLOCK: [2014-10-15 Wed 13:12]--[2014-10-15 Wed 13:28] = 0:16 CLOCK: [2014-10-15 Wed 11:44]--[2014-10-15 Wed 11:59] = 0:15 CLOCK: [2014-10-15 Wed 10:48]--[2014-10-15 Wed 10:53] = 0:05 CLOCK: [2014-10-13 Mon 18:23]--[2014-10-13 Mon 19:10] = 0:47 CLOCK: [2014-10-10 Fri 17:52]--[2014-10-10 Fri 18:55] = 1:03 CLOCK: [2014-09-10 Wed 14:29]--[2014-09-10 Wed 16:29] = 2:00 CLOCK: [2014-11-12 Wed 08:34]--[2014-11-12 Wed 08:52] = 0:18 CLOCK: [2014-11-04 Tue 12:58]--[2014-11-04 Tue 13:28] = 0:30 Best regards, Chai
Re: [O] autoloads not working correctly for org-table.el?
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Eric Abrahamsen e...@ericabrahamsen.net writes: I don't actually know what the right thing to do is. Maybe just a (require 'org-table) inside `orgstruct++-mode'? Autoload doesn't seem to work for variables, nor is there a `declare-variable'... Either (require 'org-table) in org-adaptive-fill-function or applying the following patch should fix your problem. Thank you. However, I eventually applied a different patch. I don't know what is the right thing either © e.g. I have no idea why this function has special-casing for 'message-mode (it should perhaps have special casing for when orgstruct++-mode is active, instead ?) Ideally, we should extract all orgstruct code from Org core (org-footnote.el also contains code related to Message mode) and move it to an org-struct.el or some such library. Regards, -- Nicolas Goaziou
Re: [O] Citation syntax: a revised proposal
Hi Stefan,
Stefan Nobis stefan...@snobis.de writes:
Aaron Ecay aarone...@gmail.com writes:
I count roughly 50 commands in sections 3.7.1 – 3.7.6 of the
biblatex user’s manual (version 2.9a of 24/06/2014). Some of these
are quite esoteric, of course, but they are all provided.
There are many commands (and even more private commands are possible)
in order to help reproducing all the various citation styles out there.
The critical question for org and org users is: How many different
citation commands are needed in a single document (or needed by a
single author within all her documents)?
These are very different questions. I think we need to answer the
second, since the syntax for citations will be common to all documents.
If no single author ever needs more than about a dozen different
commands (including variations like the genetive versions), the
[cite:subcommand ...] syntax should suffice.
Yes, I don't disagree. But how do we know that no single author ever
needs more than a dozen different types/commands, across all her
documents, now and in the future? I for one do not feel comfortable
making this judgment a priori. As Aaron said, it's an empirical
question.
By way of illustration, Biblatex (AFAICT) doesn’t provide a
possessive citation command, which was mentioned by someone in this
thread (or its predecessor) as a desideratum. I’d expect a savvy
latex user to put in their preamble:
\newcommand{\citeposs}[1]{\citeauthor{#1}’s (\citeyear{#1})}
This is what the subcommand is for. An author may define poss as a
subcommand and use [cite:poss ...]. Then all the nice gimmicks will
still work.
If I understand correctly, Aaron and I have two worries about this
approach. First, doing things this way potentially leads to a lot of
redundancy in the code you have to write when defining subtypes, which
is a maintenance hassle and an extra burden on users. Second, it means
that an author who has to deal with a lot of `uncommon' commands has to
remember a lot of subtype names, which are likely to be very similar,
because they represent overlapping groups of options.
Look at, e.g., the commands required in BibLaTeX to support citing
multi-volume works. There are 24(!) of them, because every one of them
is simply a multi-volume version of other combinations of options that
BibLaTeX supports (multi-cite or not? parenthetical or in-text?
footnoted or not? etc.).
For my part, if I were citing multi-volume works a lot, I would
appreciate being able to express all those options using orthogonal
distinctions. Then I could just add
{... :volume 2 ...}
at the end of a citation that already expresses most of those options in
the [cite: ...] part of the syntax. I would personally prefer *not* to
have to write
[cite/SUBTYPE: ...]
and remember which, among those 24 command types, I need to use (and
define) here.
(Also, note that this syntax does not have a way to pass additional
arguments like the volume, so it *can't* say cite volume 2, even if
with a subtype label it can say cite this multi-volume work. Citing a
volume in a multi-volume work seems like it might require some ugly
hacking on the subtypes approach, but I have no idea how often people
actually use such citations.)
On the other hand, Tom says that he prefers the latter way of working,
even if it requires a lot of subtypes. This is because it makes the
subtype easy to find-and-replace when changing a document from one
citation style to another. Also, it is simpler to write custom handlers
that dispatch just on the subtype, rather than on a plist of options.
So there are considerations on both sides. In the end, I prefer the
[cite: ...]{:key val ...}
syntax because:
1) it supports both styles of working (subtypes can be represented
like `:type fvolcites')
2) it allows passing additional arguments (e.g., volume number)
3) something like this is needed anyway elsewhere in Org
but I recognize there are some drawbacks to this over the simpler
approach of subtype labels.
Best,
Richard
Re: [O] Here is a patch I want to add to org.el……
Actually， I’m just talking about ‘org-toggle-latex-fragment’…… I'm not sure if the patch proposed may cause any other problems, but I think this feature should be added by someone. Thank you for your guide. Sent from Windows Mail From: Nicolas Goaziou Sent: Friday, February 27, 2015 5:49 PM To: Andreas Leha Cc: emacs-orgmode@gnu.org Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: I haven't looked at the patch and I do not understand how the patch achieves the removal of single overlays. But I am in the same boat. I also would (usually) like to remove only the rendered formula at the point. I think that this should even be the default. What Org version do you use? In development branch, C-c C-c doesn't remove overlays related to images and formulas. If you're talking about `org-toggle-latex-fragment', I don't think this is an issue because images are cached, so showing them again is very fast. Regards, -- Nicolas Goaziou
[O] org-clock-into-drawer not respecting setting?
Hi, I have set this variable org-clock-into-drawer is a variable defined in `org-clock.el'. Its value is 6 Original value was t Clocking in with C-c C-x C-i always creates a logbook drawer. Can anybody confirm the setting is not regarded in the latest Org version? Worked in the past. Org-mode version 8.3beta (release_8.3beta-877-g1c5db2 Thank you. Regards, Rainer
Re: [O] [patch, ox-html] mathjax changes
Rasmus ras...@gmx.us writes: Hi, Rasmus ras...@gmx.us writes: and *why* is orgmode.org hosting it? Privacy? I don't think CDN service was available at the time mathjax support was implemented. IMO, it hardly makes sense to host it now. This patch switches the cdn to upstream and removes a lot of stuff that I believe mathjax will figure out on it own. I'm no mathjax or webs export, though. Notably, mathml stuff is gone. OTOH, I added some display options, which I believe one might care about. If more user-sensible options exists I can add them. It would be good if someone who knows MathJax better could reviews this. Added font, better scale support, linebreaks, linebreaks and possibility for the browser to chose MathMl if support is good enough. If you are uncomfortable with Org linking against cdn.mathjax.org it would be good to let me know. If no other inputs, I will install this patch soonish. Pushed in 8c54b254b12d07136dc1720d2161b8a6db1f50b9. -- Warning: Everything saved will be lost
Re: [O] Here is a patch I want to add to org.el……
Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: I haven't looked at the patch and I do not understand how the patch achieves the removal of single overlays. But I am in the same boat. I also would (usually) like to remove only the rendered formula at the point. I think that this should even be the default. What Org version do you use? In development branch, C-c C-c doesn't remove overlays related to images and formulas. If you're talking about `org-toggle-latex-fragment', I don't think this is an issue because images are cached, so showing them again is very fast. I am talking about `org-toggle-latex-fragment'. And even if that is fast, it is very annoying behaviour. I'd very much like to be able to toggle individual images. In a math-heavy document the redisplay of all formula images of even the current section takes noticable moment. But much worse: if I am working on a formula, I usually like to see other formulas as images. But they disappear as soon as I switch off the image of the current formula to debug it. It is quite hard to even achieve the state where all formulas except the formula under the point are displayed as image. And I'd expect `org-toggle-latex-fragment' to do what its name suggests: to toggle the latex fragment, i.e. to produce the same state after the second invocation. Similarly to visibility cycling only a prefix should act globally, IMO. Regards, Andreas
Re: [O] Here is a patch I want to add to org.el……
Andreas Leha andreas.l...@med.uni-goettingen.de writes: I am talking about `org-toggle-latex-fragment'. And even if that is fast, it is very annoying behaviour. I'd very much like to be able to toggle individual images. In a math-heavy document the redisplay of all formula images of even the current section takes noticable moment. But much worse: if I am working on a formula, I usually like to see other formulas as images. But they disappear as soon as I switch off the image of the current formula to debug it. It is quite hard to even achieve the state where all formulas except the formula under the point are displayed as image. And I'd expect `org-toggle-latex-fragment' to do what its name suggests: to toggle the latex fragment, i.e. to produce the same state after the second invocation. Similarly to visibility cycling only a prefix should Wouldn't the correctᵀᴹ behavior be to show the latex-code under the image if point is at image. Like in AUCTeX? [I don't know if it's easily feasible to have similar behavior]. Personally, I never use org-toggle-latex-fragment, but rely on entities, since org-toggle-latex-fragment is only really good for static/mature documents. —Rasmus -- And I faced endless streams of vendor-approved Ikea furniture. . .
Re: [O] Here is a patch I want to add to org.el……
what if search for ‘org-remove-latex-fragment-image-overlays’ in org.el ? I see it in the function ‘org-ctrl-c-ctrl-c’ (org 8.2.10) Sent from Windows Mail From: Nicolas Goaziou Sent: Saturday, February 28, 2015 1:32 AM To: kuangd...@163.com Cc: Andreas Leha, emacs-orgmode@gnu.org kuangd...@163.com writes: I'm not sure if the patch proposed may cause any other problems, but I think this feature should be added by someone. Your patch is about C-c C-c, which is no longer related to `org-toggle-latex-fragment'. So, it cannot be applied. Regards,
Re: [O] Here is a patch I want to add to org.el……
kuangd...@163.com writes: what if search for ‘org-remove-latex-fragment-image-overlays’ in org.el ? I see it in the function ‘org-ctrl-c-ctrl-c’ (org 8.2.10) You wouldn't see it if you were using the development version (aka the master branch). What Nicolas said is that that no longer happens in the master branch of the git repo. The behaviour was changed with this commit: , | commit 9e006d112839de127c7e48b5c3bd292111b307b0 | Author: Bastien Guerry b...@altern.org | Date: Sun Jul 27 19:44:40 2014 +0200 | | org.el (org-ctrl-c-ctrl-c): Don't remove LaTeX fragments overlays | | * org.el (org-ctrl-c-ctrl-c): Don't remove LaTeX fragments overlays. ` You are on org 8.2.10 which is found somewhere along the maintenance branch. The maintenance branch was split off the master branch at some point in the past and has only been getting bug fixes since then: that's its purpose in life. It explicitly does *not* get any other changes. BTW, bugs in this context means things that cause severe problems: corruptions, crashes etc; it does not mean things that I don't like. So this change was not appropriate for the maintenance branch. If you want the modified behaviour, you need to install from git and use the master branch. HTH, Nick Sent from Windows Mail From: Nicolas Goaziou Sent: Saturday, February 28, 2015 1:32 AM To: kuangd...@163.com Cc: Andreas Leha, emacs-orgmode@gnu.org kuangd...@163.com writes: I'm not sure if the patch proposed may cause any other problems, but I think this feature should be added by someone. Your patch is about C-c C-c, which is no longer related to `org-toggle-latex-fragment'. So, it cannot be applied. Regards,
Re: [O] Citation syntax: a revised proposal
Aaron Ecay aarone...@gmail.com writes:
I count roughly 50 commands in sections 3.7.1 – 3.7.6 of the
biblatex user’s manual (version 2.9a of 24/06/2014). Some of these
are quite esoteric, of course, but they are all provided.
There are many commands (and even more private commands are possible)
in order to help reproducing all the various citation styles out there.
The critical question for org and org users is: How many different
citation commands are needed in a single document (or needed by a
single author within all her documents)?
If no single author ever needs more than about a dozen different
commands (including variations like the genetive versions), the
[cite:subcommand ...] syntax should suffice.
By way of illustration, Biblatex (AFAICT) doesn’t provide a
possessive citation command, which was mentioned by someone in this
thread (or its predecessor) as a desideratum. I’d expect a savvy
latex user to put in their preamble:
\newcommand{\citeposs}[1]{\citeauthor{#1}’s (\citeyear{#1})}
This is what the subcommand is for. An author may define poss as a
subcommand and use [cite:poss ...]. Then all the nice gimmicks will
still work.
--
Until the next mail...,
Stefan.
Re: [O] Here is a patch I want to add to org.el……
kuangd...@163.com writes: Here comes the reason: “C-c C-c” always removes all overlays in org files (such as formulas, images .etc )，but sometimes I only want to edit one and leave the others as it is (overlay). so, I modified the org.el .(maybe I should use “advice”……) Do you think it is deserved to patch it? In development branch, C-c C-c no longer removes overlays from images and formulas. You may want to update Org and try again. I don't think this patch is needed. Regards,
Re: [O] Here is a patch I want to add to org.el……
Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: I haven't looked at the patch and I do not understand how the patch achieves the removal of single overlays. But I am in the same boat. I also would (usually) like to remove only the rendered formula at the point. I think that this should even be the default. What Org version do you use? In development branch, C-c C-c doesn't remove overlays related to images and formulas. If you're talking about `org-toggle-latex-fragment', I don't think this is an issue because images are cached, so showing them again is very fast. Regards, -- Nicolas Goaziou
Re: [O] nicer error message when accessing killed buffer.
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: I'd like to suggest the following trivial patch: Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] autoloads not working correctly for org-table.el?
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Eric Abrahamsen e...@ericabrahamsen.net writes: I don't actually know what the right thing to do is. Maybe just a (require 'org-table) inside `orgstruct++-mode'? Autoload doesn't seem to work for variables, nor is there a `declare-variable'... Either (require 'org-table) in org-adaptive-fill-function or applying the following patch should fix your problem. Thank you. However, I eventually applied a different patch. I don't know what is the right thing either © e.g. I have no idea why this function has special-casing for 'message-mode (it should perhaps have special casing for when orgstruct++-mode is active, instead ?) Ideally, we should extract all orgstruct code from Org core (org-footnote.el also contains code related to Message mode) and move it to an org-struct.el or some such library. Regards, Thanks!
Re: [O] Citation syntax: a revised proposal
Aaron Ecay aarone...@gmail.com writes:
In this design, the potential explosion in subtypes has been pretty well
kept in check. Does that make the design of BibLaTeX a good model for
Org mode?
I don’t know, but I suspect not. Latex allows users to create powerful
macros, but has relatively few built-in niceties (some are provided by
auctex and friends, but that’s separate). Org’s macro facilities,
though also powerful, are not well-integrated into its considerable
interactive features.
By way of illustration, Biblatex (AFAICT) doesn’t provide a possessive
citation command, which was mentioned by someone in this thread (or its
predecessor) as a desideratum.
^^^
According to my dictionary, that might be a bit strong. It was used an
example of why you need userwritten types.
I’d expect a savvy latex user to put in
their preamble:
\newcommand{\citeposs}[1]{\citeauthor{#1}’s (\citeyear{#1})}
That doesn’t really work in org. (It could be put together with an org
macro, but would lose the kind of click-to-view functionality that
org-ref already provides and which would be ported to the new syntax as
well.)
And this is why I say that you need to be able to define you own subtypes.
Adding the naïve version of citepos should be something like:
(cite-mapcar (λ (cite) (concat (citeauthor cite) 's (citeyear cite))) cites)
—Rasmus
--
Got mashed potatoes. Ain't got no T-Bone. No T-Bone
[O] autoloads not working correctly for org-table.el?
Hi, I've got this in my message-mode-hook: 'turn-on-orgstruct++ It does just what I want, except the variable orgtbl-line-start-regexp isn't loaded, which wrecks auto-fill. Line 22894 of org.el has this: (defvar orgtbl-line-start-regexp) ; From org-table.el But that doesn't actually *load* the value of that variable, so using orgstruct++ mode gives me a bunch of these: Symbol's value as variable is void: orgtbl-line-start-regexp every time point gets past fill column, and the filling thing kicks in. I don't actually know what the right thing to do is. Maybe just a (require 'org-table) inside `orgstruct++-mode'? Autoload doesn't seem to work for variables, nor is there a `declare-variable'... Eric
Re: [O] Citation syntax: a revised proposal
Samuel Wales samolog...@gmail.com writes:
If you don't allow a generalized link to follow a
user-specified λs then you don't have a flexible syntax
that you expressed desire for above. You'd still have to
wait for somebody upstream to develop [color-start:⋯].
not sure why you are talking about links.
'Cause [type/subtype: whaterver]{:key val} or [type/subtype:
whaterver :key val] is like links, only meant to operate as functions,
treating data. Much like links are used, making the description part
rather annoying at times...
you can write color-start as a user. you can even define a
feature that requires a lambda: $[rasmus-color-start (lambda
(x) (rasmus-stuff))]. or $[rasmus-color ...].
but if we are going to define citations with this syntax,
then we can do so strictly. no need for lambda.
Consider:
[cite/color-me-pink:this will be pink]
The subtype is color-me-pink. Color-me-pink is a user-written function (a
λ). E.g.
(add-to-cite-types color-me-pink (lambda (cite) (my/pink cite)))
Note that this example can already be implemented via macros.
maybe you are saying that you don't think it's a good idea
to allow other first atoms. not sure why.
No. I would be thrilled about that. It would be much better than links
for most purposes.
But it's a different issue.
also, those adjectives are up to the developers.
Agreed.
—Rasmus
--
Hooray!
Re: [O] Here is a patch I want to add to org.el……
Andreas Leha andreas.l...@med.uni-goettingen.de writes: I am talking about `org-toggle-latex-fragment'. And even if that is fast, it is very annoying behaviour. I'd very much like to be able to toggle individual images. In a math-heavy document the redisplay of all formula images of even the current section takes noticable moment. But much worse: if I am working on a formula, I usually like to see other formulas as images. But they disappear as soon as I switch off the image of the current formula to debug it. It is quite hard to even achieve the state where all formulas except the formula under the point are displayed as image. And I'd expect `org-toggle-latex-fragment' to do what its name suggests: to toggle the latex fragment, i.e. to produce the same state after the second invocation. Similarly to visibility cycling only a prefix should act globally, IMO. Fair enough. Would you mind testing the following patch, then? It makes `org-toggle-latex-fragment' behave more to your liking. Regards, From 4fecb645b6c03118ba46d508ceb9159018a5d6f4 Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou m...@nicolasgoaziou.fr Date: Sat, 28 Feb 2015 00:30:43 +0100 Subject: [PATCH] Change `org-toggle-latex-fragment' behaviour * lisp/org.el (org-remove-latex-fragment-image-overlays): Allow to limit overlay removal through optional arguments. Define a new return value. (org-toggle-latex-fragment): Change behaviour. Update docstring accordingly. The new behaviour is the following: - With a double prefix argument, toggle overlays buffer wide; - With a single prefix overlay, or if there is no latex fragment at point, toggle overlays in the current section; - Otherwise, toggle overlay at point. Suggested-by: kuangd...@163.com http://permalink.gmane.org/gmane.emacs.orgmode/95492 --- lisp/org.el | 133 +--- 1 file changed, 82 insertions(+), 51 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index d05a7b8..cd5c5be 100755 --- a/lisp/org.el +++ b/lisp/org.el @@ -18748,65 +18748,96 @@ looks only before point, not after. List of overlays carrying the images of latex fragments.) (make-variable-buffer-local 'org-latex-fragment-image-overlays) -(defun org-remove-latex-fragment-image-overlays () - Remove all overlays with LaTeX fragment images in current buffer. - (mapc 'delete-overlay org-latex-fragment-image-overlays) - (setq org-latex-fragment-image-overlays nil)) +(defun org-remove-latex-fragment-image-overlays (optional beg end) + Remove all overlays with LaTeX fragment images in current buffer. +When optional arguments BEG and END are non-nil, remove all +overlays between them instead. Return t when some overlays were +removed, nil otherwise. + (let (removedp) +(setq org-latex-fragment-image-overlays + (let ((beg (or beg (point-min))) + (end (or end (point-max + (org-remove-if + (lambda (o) + (let ((s (overlay-start o)) + (e (overlay-end o))) + (cond + ((= s e) + (delete-overlay o) t) + ((and (= s beg) (= e end)) + (delete-overlay o) + (or removedp (setq removedp t)) + org-latex-fragment-image-overlays))) +removedp)) (define-obsolete-function-alias 'org-preview-latex-fragment 'org-toggle-latex-fragment 24.4) -(defun org-toggle-latex-fragment (optional subtree) +(defun org-toggle-latex-fragment (optional arg) Preview the LaTeX fragment at point, or all locally or globally. + If the cursor is in a LaTeX fragment, create the image and overlay -it over the source code. If there is no fragment at point, display -all fragments in the current text, from one headline to the next. With -prefix SUBTREE, display all fragments in the current subtree. With a -double prefix arg \\[universal-argument] \\[universal-argument], or when \ -the cursor is before the first headline, -display all fragments in the buffer. -The images can be removed again with \\[org-toggle-latex-fragment]. +it over the source code, if there is none, or remove it otherwise. +If there is no fragment at point, display all fragments in the +current section. + +With prefix ARG, preview or clear image for all fragments in the +current section. With a double prefix ARG \\[universal-argument] \ +\\[universal-argument] preview or clear +images for all fragments in the buffer. (interactive P) (unless (buffer-file-name (buffer-base-buffer)) (user-error Can't preview LaTeX fragment in a non-file buffer)) - (if org-latex-fragment-image-overlays - (progn (org-remove-latex-fragment-image-overlays) - (message LaTeX fragments images removed)) -(when (display-graphic-p) - (org-remove-latex-fragment-image-overlays) - (org-with-wide-buffer - (let (beg end msg) - (cond - ((equal subtree '(16)) - (setq beg (point-min) end (point-max) - msg Creating images for buffer...%s)) - ((equal subtree '(4)) - (org-back-to-heading) - (setq beg (point) end
Re: [O] Here is a patch I want to add to org.el……
Hi Rasmus, Rasmus ras...@gmx.us writes: Andreas Leha andreas.l...@med.uni-goettingen.de writes: I am talking about `org-toggle-latex-fragment'. And even if that is fast, it is very annoying behaviour. I'd very much like to be able to toggle individual images. In a math-heavy document the redisplay of all formula images of even the current section takes noticable moment. But much worse: if I am working on a formula, I usually like to see other formulas as images. But they disappear as soon as I switch off the image of the current formula to debug it. It is quite hard to even achieve the state where all formulas except the formula under the point are displayed as image. And I'd expect `org-toggle-latex-fragment' to do what its name suggests: to toggle the latex fragment, i.e. to produce the same state after the second invocation. Similarly to visibility cycling only a prefix should Wouldn't the correctᵀᴹ behavior be to show the latex-code under the image if point is at image. Like in AUCTeX? [I don't know if it's easily feasible to have similar behavior]. I agree that this would be nice. But additionally, I'd think. My expectation about toggling latex fragments would still be that it would by default only toggle the current fragment. Maybe that would be less of an issue if the code was visible as well. Personally, I never use org-toggle-latex-fragment, but rely on entities, since org-toggle-latex-fragment is only really good for static/mature documents. I am not sure I understand that. What do you mean when you rely on entities? Just the replacements for \alpha, ...? I think they do not help too much for the more complicated formulas. Maybe I am just out of training when it comes to reading LaTeX... Regards, Andreas
Re: [O] org-clock-into-drawer not respecting setting?
Hello, Rainer Stengele rainer.steng...@online.de writes: I have set this variable org-clock-into-drawer is a variable defined in `org-clock.el'. Its value is 6 Original value was t Clocking in with C-c C-x C-i always creates a logbook drawer. Can anybody confirm the setting is not regarded in the latest Org version? Worked in the past. This should be fixed in 18685d98527e0479b8108cac420b23d481fd5bfd. Thank you. Regards, -- Nicolas Goaziou
