Re: [PATCH] org-capture: Update plist before finalizing
Leo Vivier writes: > Hi there, > > I’m working on the parallelisation of `org-capture' for Org-roam, and > I’ve run into a problem with the updating of `org-capture-plist'. > > ;;- > ;; DESCRIPTION > ;;- > We use the global-variable `org-capture-plist' to populate the > local-variable `org-capture-current-plist' on the init of the > `org-capture' buffer. However, we do not do the opposite (i.e. update > the global-variable with the local-variable) on `org-capture-finalize'. > > This is fine for the majority of `org-capture-finalize', since we’re > using the LOCAL arg of `org-capture-get' to read > `org-capture-current-plist' instead of `org-capture-list', but this > trick does not work for `org-capture-after-finalize', since the hook is > run after the `org-capture-buffer' has been closed. > > This causes problem with `:kill-buffer t', and it limits what can be > done with cleanup functions in `org-capture-after-finalize'. [...] > ;;- > ;; PATCH > ;;- > I propose to update `org-capture-plist' early in `org-capture-finalize'. > I don’t think this would have unforeseen effects, since > `org-capture-list' is already meant to be transient, and we’d only be > expanding its use from init-only to init-and-exit. Thanks for the detailed write-up and the patch (and sorry for the slow reply). Based on a quick glance, I too think this would be safe to do. > Subject: [PATCH] org-capture: Update plist before finalizing > > * lisp/org-capture.el (org-capture-finalize): Update > `org-capture-plist' with local-value before finalizing. It'd be good to at least point to the motivation/usecase for this change here. (Your description section above already does a nice job of that.) > --- > lisp/org-capture.el | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/lisp/org-capture.el b/lisp/org-capture.el > index 2cc1ce394..223ed4124 100644 > --- a/lisp/org-capture.el > +++ b/lisp/org-capture.el > @@ -728,6 +728,9 @@ captured item after finalizing." > >(run-hooks 'org-capture-prepare-finalize-hook) > > + ;; Update `org-capture-plist' with the local-value > + (setq org-capture-plist org-capture-current-plist) Convention nit: please end your comment with a period. Perhaps add a brief mention of `org-capture-after-finalize' (or some other hint of why) here.
Putting the value of page-delimiter in some outline regexps?
Hi all, I've been trying to find a way to cordon off the bottom of my Org files, to create an area for file-local variables and "LocalWords" and what have you that Org doesn't consider part of the file's final heading. The usual Emacs thing to do seems to be using the value of page-delimiter to demarcate the end of content, and the beginning of meta data. I stuck that into the value of `org-outline-regexp', and also hard-coded it into the "true heading" branch of `org-end-of-subtree'. Over the past day this has worked fine for interactive use, and some automatic Org-based tools. But I'm not so naive as to think that catastrophic breakage couldn't be right around the corner as a result of this! Anyway, I wanted to see if anyone else had tried this, or had any ideas about it. Eric
Re: Website revamp?
Tom Gillespie writes: > Oop, one other thing. There is no obvious way back when clicking view > source, and the button disappears out from under the mouse which is > quite annoying. Is it possible to retain the header so that one can > toggle the view of the main page and the source simply by repeatedly > clicking/tapping? Best, > Tom Done! Via an iframe.
Re: Website revamp?
Hi Tom, Thanks for your emails, they're most helpful! I'll respond to them one at a time. Tom Gillespie writes: > When the dimensions of the browser window become too narrow the links in > the header move to the hamburger menu. This seems like it is quite bad > for discoverability. Is there a way that the other sections could be > concatenated/loaded on scroll if it were that narrow? This is how it originally was, but that ended up looking messy. Given the hamburger is a common design, I think visitors should know what to do with it :D > Relatedly, it > seems like it might be better to simply show the features directly > below the banner on the home page rather than having users click > through. That is the question that many users will be asking at that > point in the page, and having the answer there waiting for them seems > like it would be helpful. I'm not always a fan of the long scroll > single page approach to this, but it seems like it might make sense > for the narrow screen case. I'm thinking I'll just try to /very/ prominently link to features. Something like the markdown guide's set of three big icons + text could work (https://www.markdownguide.org/). Thanks for your feedback! Timothy
Re: [feature request] A new cookie type [!] showing the last note taken
>> - \\ >> > > This is not specific enough to be considered as syntax. The risk of > false positive is too high. This is the reason why notes were never > considered as syntactically meaningful so far. I may miss something, but it does not look [for me] any more specific in comparison with headline format: - headline :: "^\*+ .+$" - first line of note :: "^[ \t]*-.+$" Body of the note can be extracted using existing item parser (removing the first line). >> The is taken from `org-log-note-headings'. > > This is configurable, which is not a good idea for any new syntax. Agree. The syntax may allow arbitrary first line instead of limiting it to `org-log-note-headings'. Though `org-log-note-headings' can still be used to define special types of notes - not a part of syntax, but for org-mode functionality in Emacs. Best, Ihor Nicolas Goaziou writes: > Hello, > > Ihor Radchenko writes: > >> Instead of linking to the function, we can define the format used by >> `org-add-note' as a formal format for notes. Currently `org-add-note' >> uses the following format: >> >> - \\ >> > > This is not specific enough to be considered as syntax. The risk of > false positive is too high. This is the reason why notes were never > considered as syntactically meaningful so far. > >> The is taken from `org-log-note-headings'. > > This is configurable, which is not a good idea for any new syntax. > > Regards, > -- > Nicolas Goaziou
Re: Headline generation as in diary?
Robert Pluim writes: > Itʼs triggered by the %%(, I believe, but not in headlines. Yes, I see that in the code. But actually I seem to have the opposite problem: I can't make the original headline appear in the agenda. When the sexp doesn't return a string the agenda will contain a line saying "SEXP entry returned empty string" instead of showing the headline. > You can use them in timestamps as well, which is useful for weird time > periods > > ** Just before midnight on a few days 23:00-24:00 > <%%(org-block 2020 8 31 2020 9 2)> > <%%(org-block 2020 9 10 2020 9 12)> But it seems those time stamps are not allowed to span multiple lines (at least I don't get it work). Seems org doesn't recognize them as such? Michael.
Re: auto-completion for file paths?
Dmitrii Korobeinikov writes: > Hi, all! > > Is there a way to provide completions for paths > [[file:suggest/completions/here]]? org-insert-link (C-c C-l) will read a file name from you if you select "file:" or call it with a prefix argument.
auto-completion for file paths?
Hi, all! Is there a way to provide completions for paths [[file:suggest/completions/here]]? Best, DK
Re: latex fragments compilation error when exporting to html
Hello,
Some follow up on this problem
I thought that I messed up the org-mode update because I had some
org files open during the updates.
I reinstall emacs and org-mode to the latest but I still get the
problem. Performing M-x org-html-export-to-html on the file below ends
up in an error because tabular* is wrongly added instead of tabular.
I could reproduce the problem with the version org-mode that comes with
the latest emacs version as well.
-- test.org
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t
tex:imagemagick title:nil author:nil date:nil
#+LATEX_HEADER: \usepackage{booktabs}
\begin{tabular}{lll}
\toprule
4 & 2 & 3 \\
5 & 6 & 8 \\
\hline
\end{tabular}
\end{table}
Best regards,
Jeremie
GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5,
cairo version 1.16.0) of 2020-09-01
Org mode version 9.3.7 (release_9.3.7-725-g7bc18e @
/home/djj/src/org-mode/lisp/)
Re: Website revamp?
Oop, one other thing. There is no obvious way back when clicking view source, and the button disappears out from under the mouse which is quite annoying. Is it possible to retain the header so that one can toggle the view of the main page and the source simply by repeatedly clicking/tapping? Best, Tom On Tue, Sep 1, 2020 at 11:07 AM Tom Gillespie wrote: > > Hi Timothy, > Thank you for all your work on this! A couple of suggestions. When > the dimensions of the browser window become too narrow the links in > the header move to the hamburger menu. This seems like it is quite bad > for discoverability. Is there a way that the other sections could be > concatenated/loaded on scroll if it were that narrow? Relatedly, it > seems like it might be better to simply show the features directly > below the banner on the home page rather than having users click > through. That is the question that many users will be asking at that > point in the page, and having the answer there waiting for them seems > like it would be helpful. I'm not always a fan of the long scroll > single page approach to this, but it seems like it might make sense > for the narrow screen case. Best! > Tom > > On Tue, Sep 1, 2020 at 9:44 AM TEC wrote: > > > > > > Hello everyone :) > > > > The end is now in sight! Other than the somewhat bare index page, I feel > > that we're nearing complete coverage of the current site (at least all > > the 'main' pages). > > > > If you haven't already please give my revamp project a look: > > http://orgmode.tecosaur.com, and let me know if you've got any feedback > > or suggestions. > > > > Hopefully I'll be able to hear from Bastien at some point to get his > > thoughts on this branch, and to see if he'd be willing to have this > > replace the current site (eventually) :) > > > > All the best, > > > > Timothy. > >
Re: Website revamp?
Hi Timothy, Thank you for all your work on this! A couple of suggestions. When the dimensions of the browser window become too narrow the links in the header move to the hamburger menu. This seems like it is quite bad for discoverability. Is there a way that the other sections could be concatenated/loaded on scroll if it were that narrow? Relatedly, it seems like it might be better to simply show the features directly below the banner on the home page rather than having users click through. That is the question that many users will be asking at that point in the page, and having the answer there waiting for them seems like it would be helpful. I'm not always a fan of the long scroll single page approach to this, but it seems like it might make sense for the narrow screen case. Best! Tom On Tue, Sep 1, 2020 at 9:44 AM TEC wrote: > > > Hello everyone :) > > The end is now in sight! Other than the somewhat bare index page, I feel > that we're nearing complete coverage of the current site (at least all > the 'main' pages). > > If you haven't already please give my revamp project a look: > http://orgmode.tecosaur.com, and let me know if you've got any feedback > or suggestions. > > Hopefully I'll be able to hear from Bastien at some point to get his > thoughts on this branch, and to see if he'd be willing to have this > replace the current site (eventually) :) > > All the best, > > Timothy. >
Re: Mass conversion of items
On Tue, Sep 01, 2020 at 06:22:02PM +0100, Sharon Kimble wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Thanks for replying Tomas.
>writes:
You're welcome :-)
[...]
> >> - --8<---cut here---start->8---
> >> \uuline{foo}
> >> - --8<---cut here---end--->8---
[...]
> >> - --8<---cut here---start->8---
> >> /\uuline{foo}/
> >> - --8<---cut here---end--->8---
[...]
> Okay, being very specific, all of '\uuline{foo}' remains, but with a
> forward slash at the beginning and end of '\uuline{foo}' to achieve this
> '/\uuline{foo}/'
Ah, got it now. Regular expressions seem to be your friends here.
I'm assuming your foo is a placeholder, and varies from instance
to instance. I'm further assuming the "foo"s don't contain a closing
curly brace (we'd have to refine things otherwise).
Try M-x (i.e. Meta-x) and then "query-replace-regexp". It asks you
first for the regular expression, which will be
\\uuline{[^}]*}
(note the double backslash: that's because a backslash has a special
meaning in regular expressions, and you have to "escape" it with another
backslash; this regexp roughly states: "a backslash followed by uuline,
followed by an opening curly, followed by zero or more (that's the star)
characters which aren't a closing curly followed by a closing curly).
You finish that part with ENTER. Then you're asked for the replacement.
You enter
/\&/
Which means: "a slash, followed by whatever you just matched (that's
the "\&" part, only one backslash this time) and a slash.
Make a backup of your file first :-)
Regular expressions are very powerful, but sometimes confusing. It pays
off big time to wrangle them!
Good luck
- t
signature.asc
Description: Digital signature
Re: Mass conversion of items
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks for replying Tomas.
writes:
> On Tue, Sep 01, 2020 at 04:09:27PM +0100, Sharon Kimble wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> I'm hoping that someone can help with this problem I have.
>>
>> I have several org-mode files which have some specific formatting in
>> individual items, specifically -
>>
>> - --8<---cut here---start->8---
>> \uuline{foo}
>> - --8<---cut here---end--->8---
>>
>> This gives a double-underling of 'foo' when exported to latex and built
>> into a pdf file.
>>
>> I'm now in the situation when the double underlining also needs to be
>> italicised, and in org-mode its showing as -
>>
>> - --8<---cut here---start->8---
>> /\uuline{foo}/
>> - --8<---cut here---end--->8---
>>
>> This gives a double-underling and italicised of 'foo' when exported to
>> latex and built into a pdf file.
>>
>> I would like to change about 150+ 'foos' and possibly using
>> 'replace-string' to do it. Also, 'foo' is lots of different words which
>> includes spaces between some of them. So how can I do it please?
>
> Hm. From your description it's unclear what exactly are you
> after. A couple of questions to try to zoom into that:
>
> - You want to change the text in the curly braces, i.e. what
>you call 'foo' above? Is this text always different? Is it
>possible to state a rule describing how this text looks like
>and by what you want to replace it? Or is the process going
>to be manual?
> - All that stuff: is it in one file or scattered across multiple
>files?
Okay, being very specific, all of '\uuline{foo}' remains, but with a
forward slash at the beginning and end of '\uuline{foo}' to achieve this
'/\uuline{foo}/'
Thanks
Sharon.
>
> I'm sure there are a couple of other questions I just forget now,
> But we'll get there :)
>
> Cheers
> - t
>
- --
Debian 10.5, fluxbox 1.3.7, emacs 27.1, org 9.3.7
-BEGIN PGP SIGNATURE-
iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAl9OgzobHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INb0cYP/iJ65wP+ZIA2nPXnxZLK
OZebw3ghKx1xTFQvCXc3m5UXCjkDUgAk9sJpGdpx/FvzzHWvpmpkQkPybnyRXBwM
Ogc1PlEJRjhXMbAwyocvNmpoBMzF90c5xa3ge7qmbn9ogNr61l4oD0ZMaIjwA30k
Rsz2lzuv4GRCv3R7r6W1Y3H11ks9bt0QE3vZKgnUb7veKW50bZcJMqRwL1xGIYB4
HnuG7GNOAnTuf2dGF1BMco2NBONEYQhhL5WUksGb5nqLKDqa664BhTPHT1L6jPay
TeBfSc3gSQHU2hPp2/iiaYlvkiQFKsS6Q7wQ1+IwrYKNkbaszkRvjS9wmzV6CMc9
so4N/Dbx9LsTXlA/8YbjYbYWUGDuCBot5MJc9OjX27+uP0BqhoIux93UsjpWKAFB
e721RTLewXDtQLV/uoVxEfWGUxOKBEw7VDhyPOZ72Gxk8c7EhUQC3bLRLHDe3mZi
Y99JKXYbfL0Mcfl+5/wbD91L1BJt29+KZAqzvrYRKaU8AAHrBZcStgn1en/m5JS0
fPTXDOvTHedIdpqLz3oQIU7FAQs+RD/PbbVf+8vXcaq6k8MZeuNki2E0lBxVo/cu
FHJBnbY7o3vUDwDXMyV23IUBMLLDy4ug0dK2+NBGTM7SosJazNq4mWdMgAtWVfYi
0ARNlhp4bixDDlOwtfTkS3lQ
=kqHe
-END PGP SIGNATURE-
Re: Mass conversion of items
On 2020-09-01, at 18:19, Eric S Fraga wrote: > On Tuesday, 1 Sep 2020 at 16:09, Sharon Kimble wrote: >> I would like to change about 150+ 'foos' and possibly using >> 'replace-string' to do it. Also, 'foo' is lots of different words which >> includes spaces between some of them. So how can I do it please? > > You may wish to use replacement with regular expressions: Check info > manual for emacs, (emacs) Regexp Replace Maybe you could also use keyboard macros for that. Hth, -- Marcin Borkowski http://mbork.pl
Re: Headline generation as in diary?
Eric S Fraga writes: > On Tuesday, 1 Sep 2020 at 18:10, Robert Pluim wrote: > * Birthdays > > and then a number of %%(diary-anniversary ...) entries all under this > headline. > Note that you can also use %%(org-anniversary ...) with slightly different dependencies. I also use modifications of diary to insert sunrise and sunset. But I think that these %% functiotns only show up as part of agenda processing. -- Robert Horn rjh...@alum.mit.edu
Re: Website revamp?
Hello everyone :) The end is now in sight! Other than the somewhat bare index page, I feel that we're nearing complete coverage of the current site (at least all the 'main' pages). If you haven't already please give my revamp project a look: http://orgmode.tecosaur.com, and let me know if you've got any feedback or suggestions. Hopefully I'll be able to hear from Bastien at some point to get his thoughts on this branch, and to see if he'd be willing to have this replace the current site (eventually) :) All the best, Timothy.
Re: Website revamp?
Maxim Nikulin writes:
I do not know how much work is required to update animated
images.
Maybe someone will give better ideas, so do not hurry.
I'll store a link to this email for when I have time to revisit
this :)
- Publishing. Something wrong with HTML export of the LaTeX
macro, backslashes
are exported in description (just as on orgmode.org). Empty
braces are
necessary only if space should be kept after a TeX command, e.g.
"\TeX{} logo",
Unsure if math mode separator is required, but it should allow
omit braces. I
have tried "@@latex:\\@@LaTeX". It works, but newline is
inserted before. I
believe, it is OK to use just text LaTeX in e.g. HTML.
This has been improved.
Installation page
I am uncertain if it is applicable for other editors, but I
would like to see
name of vim plugin since ambiguity (or matter of taste) exists..
FAQ suggests
other vim plugins. I do not remember if I saw vim-outliner
somewhere on
orgmode.org. I have not tried any of these plugins.
Each entry is a link to the extension/plugin in question, is this
not sufficient?
All the best,
Timothy.
Re: Mass conversion of items
On Tuesday, 1 Sep 2020 at 16:09, Sharon Kimble wrote: > I would like to change about 150+ 'foos' and possibly using > 'replace-string' to do it. Also, 'foo' is lots of different words which > includes spaces between some of them. So how can I do it please? You may wish to use replacement with regular expressions: Check info manual for emacs, (emacs) Regexp Replace -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-725-g7bc18e
Re: Headline generation as in diary?
On Tuesday, 1 Sep 2020 at 18:10, Robert Pluim wrote: >> On Tue, 01 Sep 2020 17:18:42 +0200, Michael Heerdegen >> said: > Michael> Where in an entry do you specify such specifications? > > Below the headline, after the properties. Yes, exactly. I have one headline which says something along the lines of: * Birthdays and then a number of %%(diary-anniversary ...) entries all under this headline. I could have done these with a +1y repeat but, like Michael, like the %d capability of diary entries. I use org-recur for most other repeat items and org-clone-subtree-with-time-shift for setting up repeats with end dates (e.g. lectures in a term). -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-725-g7bc18e
Re: Mass conversion of items
On Tue, Sep 01, 2020 at 04:09:27PM +0100, Sharon Kimble wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I'm hoping that someone can help with this problem I have.
>
> I have several org-mode files which have some specific formatting in
> individual items, specifically -
>
> - --8<---cut here---start->8---
> \uuline{foo}
> - --8<---cut here---end--->8---
>
> This gives a double-underling of 'foo' when exported to latex and built
> into a pdf file.
>
> I'm now in the situation when the double underlining also needs to be
> italicised, and in org-mode its showing as -
>
> - --8<---cut here---start->8---
> /\uuline{foo}/
> - --8<---cut here---end--->8---
>
> This gives a double-underling and italicised of 'foo' when exported to
> latex and built into a pdf file.
>
> I would like to change about 150+ 'foos' and possibly using
> 'replace-string' to do it. Also, 'foo' is lots of different words which
> includes spaces between some of them. So how can I do it please?
Hm. From your description it's unclear what exactly are you
after. A couple of questions to try to zoom into that:
- You want to change the text in the curly braces, i.e. what
you call 'foo' above? Is this text always different? Is it
possible to state a rule describing how this text looks like
and by what you want to replace it? Or is the process going
to be manual?
- All that stuff: is it in one file or scattered across multiple
files?
I'm sure there are a couple of other questions I just forget now,
But we'll get there :)
Cheers
- t
signature.asc
Description: Digital signature
Re: Headline generation as in diary?
> On Tue, 01 Sep 2020 17:18:42 +0200, Michael Heerdegen > said: Michael> Eric S Fraga writes: >> No, not necessarily. I have entries like this: >> >> %%(diary-anniversary 1981 03 17) Somebody's birthday (%d years) >> >> and the agenda view shows "Somebody's birthday (19 years)"; the actual >> heading for this entry is ignored. Michael> Where in an entry do you specify such specifications? Below the headline, after the properties. >> However, I don't know if other diary- functions work the same way. They do, although there are org- versions of most (all?) of them that you should use, since they consistently use ISO8601 date order, unlike the diary functions. The manual is a bit lacking in this area, I think. Michael> Yes, the interesting part then is: when does org behave like this, and Michael> can this behavior be forced? Itʼs triggered by the %%(, I believe, but not in headlines. You can use them in timestamps as well, which is useful for weird time periods ** Just before midnight on a few days 23:00-24:00 <%%(org-block 2020 8 31 2020 9 2)> <%%(org-block 2020 9 10 2020 9 12)> Robert
Re: Headline generation as in diary?
Michael Heerdegen writes: > > [1] https://github.com/m-cat/org-recur > > Thanks for the hint, I'll have a look. Nice to have definitely. I want to stick to diary sexp expressions for some complicated dates. I have already extended the diary language to fit my needs to specify the dates of garbage collection here. That looks like this: #+begin_src emacs-lisp (dg-let-date (dg-tomorrow) (dg-except-for* (and (dg-friday-p) (cl-evenp (dg-iso-week))) (cl-some #'dg-holiday-p (dg-the-days-between (dg-days-before 2))) +1)) #+end_src It means: warn me one day before garbage collection happens, and that is: every Friday in any week with even week number, unless it has been a holiday up to two days before that, then they collect one day later. I guess I always want Lisp to specify something like this. Michael.
Re: Headline generation as in diary?
Eric S Fraga writes: > No, not necessarily. I have entries like this: > > %%(diary-anniversary 1981 03 17) Somebody's birthday (%d years) > > and the agenda view shows "Somebody's birthday (19 years)"; the actual > heading for this entry is ignored. Where in an entry do you specify such specifications? > However, I don't know if other diary- functions work the same way. Yes, the interesting part then is: when does org behave like this, and can this behavior be forced? > > Or do I miss something? How to other people deal with things > > like...garbage collection? > > I use the org-recur [1] package for this. Very nice for repeating > events. > Footnotes: > [1] https://github.com/m-cat/org-recur Thanks for the hint, I'll have a look. Michael.
Re: Headline generation as in diary?
On Tuesday, 1 Sep 2020 at 16:34, Michael Heerdegen wrote: > I would like to use my org file to specify those things instead of > maintaining a second file (the diary file). But AFAIK the dynamically > created headline part is tricky: what appears in the agenda is always > the org headline as it appears in the file, right? No, not necessarily. I have entries like this: %%(diary-anniversary 1981 03 17) Somebody's birthday (%d years) and the agenda view shows "Somebody's birthday (19 years)"; the actual heading for this entry is ignored. In fact, I have a large number of such entries all in the same headline. However, I don't know if other diary- functions work the same way. > Or do I miss something? How to other people deal with things > like...garbage collection? I use the org-recur [1] package for this. Very nice for repeating events. HTH, eric Footnotes: [1] https://github.com/m-cat/org-recur -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-725-g7bc18e
Mass conversion of items
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm hoping that someone can help with this problem I have.
I have several org-mode files which have some specific formatting in
individual items, specifically -
- --8<---cut here---start->8---
\uuline{foo}
- --8<---cut here---end--->8---
This gives a double-underling of 'foo' when exported to latex and built
into a pdf file.
I'm now in the situation when the double underlining also needs to be
italicised, and in org-mode its showing as -
- --8<---cut here---start->8---
/\uuline{foo}/
- --8<---cut here---end--->8---
This gives a double-underling and italicised of 'foo' when exported to
latex and built into a pdf file.
I would like to change about 150+ 'foos' and possibly using
'replace-string' to do it. Also, 'foo' is lots of different words which
includes spaces between some of them. So how can I do it please?
Thanks
Sharon.
- --
Debian 10.5, fluxbox 1.3.7, emacs 27.1, org 9.3.7
-BEGIN PGP SIGNATURE-
iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAl9OZCcbHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INbIKoP/jPRMgczyaMVbAYxoBco
1xnfZk6LNX3kdXxBgyFMDJIkkwGeBsPoLeC6zsW42uDe6N+Hr0+1bTI/E2uSg/I4
PybZLDAtKlWyFqjOVQASo1DC3CqHCzfr0Z66JkMj05qBJTGbIPm88PZxBSxs5ieQ
PluJYNHjcNO78AeQrY1IrrDaNco5HAqVi0pWOCjykkCQHmmTB3wrY4S4YvOmeGAF
m4SF6713o7VB2+VMgmWITSge6iHCwxHGqlabT6wRNhiZDSJHQQuEzxdg1SxaFsfe
BH7YECjDmaAP60sXbOcbLnU882QtH2qXiCFwTUchjpmQ5fGH7fUE/kKPQnnjjD7W
vq91skF1I0BMVoLuTT5FkNucMOpzxAw4RuHLZ4yWnXcrflXZPaurFnDlRTYFaA88
VkCkhxWf7WtbmcnSg3YNfP6T/nq4XLVu3zuE0DBjmRXobzULmM/ptSoydpnleawz
G7HQmSrUyBPMGX9kX7ggTWY5IvkF27CclEQL0tAR8Cui1GNBiQj9xEnWzVFcmTww
wIP3RoCAloa1RnF2OIOBlXY0w38EI+O5/F8uNogoUpHQTGWD8eSE6uhjSIXzhyC7
RtlZLSsVttpJv3uxIXOcfUFXTOMKr7wmBij9RsKSkkAbi7SabgWpeL6W+aJzR70J
Hqxr914+M4k3eEOSw197TEiJ
=WUuK
-END PGP SIGNATURE-
Headline generation as in diary?
Hi, I am mainly using the org agenda for day planning. But there is a functionality I seem to miss I know from diary: With diary, I can use arbitrary Lisp expressions to generate dates, and those expressions can also return a string to use as non-nil return value to generate non-constant headlines including certain numbers for example. I can use that to implement when the next garbage collection will come (rules for that are complicated since there are exceptions etc), add reminders for certain important stuff, etc. I would like to use my org file to specify those things instead of maintaining a second file (the diary file). But AFAIK the dynamically created headline part is tricky: what appears in the agenda is always the org headline as it appears in the file, right? Or do I miss something? How to other people deal with things like...garbage collection? TIA, Michael.
Re: latex fragments compilation error when exporting to html
> Jeremie Juste writes: > Hello, > Many thanks for your concerns. Everything goes well with emacs > -Q. Sorry for the noise. The culprit is definitely in my init > file. I'll keep the emacs -Q options in mind before sending issues > next time. >> Out of curiosity, what happens if you wrap the LaTeX in >> #+begin_export latex ... #+end_export > If I wrap I get the same error. Perhaps check that you don't have any older versions of org-mode in your system. Best wishes,
Re: latex fragments compilation error when exporting to html
Some news about the investigation. The org-mode version of the emacs -Q
is Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/local/share/emacs/26.3/lisp/org/). It's pretty old but the latex
compilation works fine.
When I change to
Org mode version 9.3.7 (9.3.7-24-g7b657c-elpa @
/home/djj/.controlled-emacs.d/elpa/org-20200831/)
The same issue arises. tabular* instead of tabular.
I don't know how to change the version of org-mode without
restarting. But with my .emacs brought to minimun and I just
uncommenting the following command.
(add-to-list 'load-path "/home/djj/.controlled-emacs.d/elpa/org-20200831")
(require 'org) is enough to generate the issue.
Best regards,
Jeremie
Eric S Fraga writes:
> On Monday, 31 Aug 2020 at 22:24, Jeremie Juste wrote:
>> When I export test.org to html, the latex fragment fail to compile.
>> The reason is a star get added to the tabular environment. {tabular*}
>> (see tmpfile.tex).
>
> Doesn't happen to me.
>
> Out of curiosity, what happens if you wrap the LaTeX in
> #+begin_export latex ... #+end_export
> ?
Re: latex fragments compilation error when exporting to html
Hello,
Many thanks for your concerns.
Everything goes well with emacs -Q. Sorry for the noise.
The culprit is definitely in my init file. I'll keep the emacs -Q
options in mind before sending issues next time.
> Out of curiosity, what happens if you wrap the LaTeX in
> #+begin_export latex ... #+end_export
If I wrap I get the same error.
Best regards,
Jeremie
Eric S Fraga writes:
> On Monday, 31 Aug 2020 at 22:24, Jeremie Juste wrote:
>> When I export test.org to html, the latex fragment fail to compile.
>> The reason is a star get added to the tabular environment. {tabular*}
>> (see tmpfile.tex).
>
> Doesn't happen to me.
>
> Out of curiosity, what happens if you wrap the LaTeX in
> #+begin_export latex ... #+end_export
> ?
Re: latex fragments compilation error when exporting to html
On Monday, 31 Aug 2020 at 22:24, Jeremie Juste wrote:
> When I export test.org to html, the latex fragment fail to compile.
> The reason is a star get added to the tabular environment. {tabular*}
> (see tmpfile.tex).
Doesn't happen to me.
Out of curiosity, what happens if you wrap the LaTeX in
#+begin_export latex ... #+end_export
?
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-724-ge8ebf5
Re: File local setting for export directory?
Eric Abrahamsen writes: > Loris Bennett writes: > >> Hi Eric, >> >> Eric Abrahamsen writes: >> >>> "Loris Bennett" writes: >>> Hi, I want to export an org file to a pdf and have the pdf created in subdirectory relative to the org file. What's the simplest way to set the export directory in a file local way? >>> >>> I suggested the attached diff a while ago, but no one seemed very >>> interested. I think it might already do what you want. >>> >>> >>> diff --git a/lisp/ox.el b/lisp/ox.el >>> index 9cf62078a..77cafb20d 100644 >>> --- a/lisp/ox.el >>> +++ b/lisp/ox.el >>> @@ -6417,6 +6417,20 @@ Return file name as a string." >>> "Output file: " pub-dir nil nil nil >>> (lambda (n) (string= extension (file-name-extension n t)) >>>extension)) >>> +(pub-dir (or pub-dir >>> + (and subtreep (org-entry-get >>> +nil "EXPORT_PUB_DIR" 'selective)) >>> + (org-with-point-at (point-min) >>> + (catch :found >>> + (let ((case-fold-search t)) >>> + (while (re-search-forward >>> + "^[ \t]*#\\+EXPORT_PUB_DIR:[ \t]+\\S-" >>> + nil t) >>> + (let ((element (org-element-at-point))) >>> + (when (eq 'keyword (org-element-type element)) >>> + (throw :found >>> +(org-element-property >>> + :value element)) >>> (output-file >>> ;; Build file name. Enforce EXTENSION over whatever user >>> ;; may have come up with. PUB-DIR, if defined, always has >>> >> >> Thanks for the patch - it is exactly what I needed. >> >> I'm surprised no-one was interested, although I suppose back then I was >> probably also one of the uninterested :-) > > Oh I'm not blaming anyone! There are a lot of patches coming down here, > and a lot of ideas for Org, and it's hard to keep up. I don't think I > did a very good job of stating my case, either. > > I actually hadn't thought of how the latex process might go haywire with > an absolute export file name. My motivation was simply that "next to my > *.org" files is pretty much never where I want exported files to end up. > I want to send them to ~/tmp, or to a directory that's shared with > colleagues via syncthing. In fact what I really want is to export to the > value of ATTACH_DIR, because then I can immediately use all the attach > tools on the exported files. > > Latex compilation is a nice additional argument, though! It's a month later and, having updated Org in the meantime, I'm having to patch again. What would be the way forward in terms of getting the patch into Org? Cheers, Loris -- This signature is currently under construction.
