Org site is down
Orgmode.org appears to be down.
Re: feature request: easy embedding of images
Jude DaShiell [2023-02-20 Mon 16:24] wrote: > To help accessibility it would be useful when an image was dragged into > org-mode if the user got prompted for an image description that gets > associated with the image in org-mode. Some images are art work and those > should get alt="" tags if a user fails to provide a description but only > after asking if this image is art work or something that needs a > description. If a description is provided that should go between the > quotes in the alt="" tag. In org-download you can specify html attributes for the attached image, see link https://github.com/abo-abo/org-download/blob/master/org-download.el#L178-L184 It's not a prompt, it's a template and you can fill the alt description. -- Daniel Fleischer
Re: feature request: easy embedding of images
Alexis Gallagher [2023-02-18 Sat 16:22] wrote: > This is a feature request — or failing that, a request for advice on a > settings configuration which could produce this > functionality now. Russell mentioned a package and pointed to the image issues related to Emacs, not Org. I want to suggest the package https://github.com/abo-abo/org-download which I use all time, for dragging and dropping images and for taking screeshots. -- Daniel Fleischer
Re: Question about deadline/schedule events date text property
Ihor Radchenko [2023-01-18 Wed 13:23] wrote: > Note that `org-fix-agenda-info' converts the 'date property back to some > other format... (yes, that's kind of crazy) Thanks, that could be useful. -- Daniel Fleischer
Re: org-todo-keywords and task sequence
Daniel Fleischer [2023-01-17 Tue 10:10] wrote: > Don't let the cyclical switching dictates the meaning, it's just an > implementation detail, done for simplicity. Hope it helped. Put another way, if you define A B | C D E and the UI switching is A->B->C->D->E->A it doesn't mean the B going into C makes sense or D going into E makes sense, it's just how the UI is built. You give meaning to the states and what states transitions are valid (in your world). Like many things, org gives some structure to work with and we need to give the meaning. -- Daniel Fleischer
Re: org-todo-keywords and task sequence
David Masterson writes: > I'm not sure I understand 'sequence' and 'type' in org-todo-keywords. You're over thinking it. You can define various todo keywords and they are divided into two groups that can be thought of as "ones that need your attention" and "ones that don't need your attention" and they are separated by a literal "|". Example: todo, in progress, on hold, waiting, phonecall etc are of the 1st type. Done, canceled, postponed are of the 2nd type. In terms of "moving" between them, it's either cyclical or you can jump to a specific word using shortcuts you define e.g. #+TODO: TODO(t) | DONE(d) Don't let the cyclical switching dictates the meaning, it's just an implementation detail, done for simplicity. Hope it helped. -- Daniel Fleischer
Question about deadline/schedule events date text property
Hi, I'm working on an unrelated project that collects events from agenda buffers. I noticed the following: when you have a series of a repeating events, scheduled events have a date text property of the form (1 9 2023) date matches the instance date while deadline events have 738529 which repeats for all instances Is this intentional? Why don't they have the same format/behavior? The setup - events have the form: * TODO Test SCHEDULED: <2023-01-09 Mon +1w> or * TODO Test DEADLINE: <2023-01-09 Mon +1w> Open an org agenda for a month and examine the text properties of the events. -- Daniel Fleischer
Re: [BUG] issue with texmathp [9.6 (release_9.6-22-g78d283 @ /home/jds6696/.emacs.d/straight/build/org-mode/)]
Ihor Radchenko writes: > Can you try to test the attached patch? Looks good. Now these work again: `cdlatex-dollar`, inserting symbols using ` outside math environments and inserting cdlatex environments with completion also outside math environments. Need to make sure the issue of the OP didn't regress. BTW, I haven't follow any discussions about org syntax and math environments inside org (the use of \...[\] instead $...$ etc.) These usecases I mentioned are what I'm used to and perhaps they are not consistent with changes made to the org syntax, demanding every math should be inside a math environment for easier parsing and you still managed to solve that without all the previous regexps. Thank you, -- Daniel Fleischer
Re: [BUG] issue with texmathp [9.6 (release_9.6-22-g78d283 @ /home/jds6696/.emacs.d/straight/build/org-mode/)]
I just found this thread after math-related things stopped working. I
have two use cases that don't work now:
1. Inserting a dollar pair $$ using `cdlatex-dollar` (it thinks we're
inside a math environment).
2. Inserting of cdlatex environments using their built-in completions, e.g.
ali
eqn
stopped working.
Previously org-cdlatex worked perfectly, you could insert \alpha using
`a and it compiled to HTML/latex (without $$), have $...$ compiled into
an inline equation and insert latex environment like
\begin{align}...\end{align} without explicit math environment and was
also compiled perfectly to HTML/latex.
--
Daniel Fleischer
Re: Intention of verbatim text?
c.bu...@posteo.jp [2023-01-03 Tue 13:20] wrote: > in org you can have inline verbatim and code text elements like this. > > Example with =verbatim= and ~code~. > > The org html export to create both with tag. So in HTML output > there is no difference between verbatim and code anymore. > > I also read a lot about the HTML tags code, pre, kbd and samp. > > The background of my question is that I have my own > org-to-html-converter [1] and try to decide how to treat =verbatim=. According to https://stackoverflow.com/questions/32284477 they have different semantics but are rendered the same (by default); they could be rendered differently, depending on a website's CSS. Maybe use the semantics for your own org-html converter. -- Daniel Fleischer
Bug? Error in HTML export of links with search options
Org offers the ability to run a search inside a link, see (org) Search Options. E.g. [[File.c::100]] to get to line 100 in File.c. When exporting this to HTML I get the following error: org-export-data: Unable to resolve link: "‘recenter’ing a window that does not display current-buffer." Also when having links of the form [[File.clj::defn]] where `defn' is a search string. Main 04d2cc59. -- Daniel Fleischer
Re: [BUG] beamer export
Hi, I'm on vacation for the next month. I can look at it when I'm back. On Thu, Sep 29, 2022, 03:44 Ihor Radchenko wrote: > Leo Butler writes: > > > The following Org document shows a bug in the beamer exporter. > > Confirmed on main. > > There are two bugs reported here: > 1. ox-latex export bug for src blocks containing direct LaTeX when >org-latex-src-block-backend is set to its default 'verbatim value > 2. ox-beamer export bug as described in the attached org file > > Daniel, can you please take a look at the first bug? > I suspect that \commands should be additionally escaped in verbatim > environment, similar to > > https://stackoverflow.com/questions/3019774/how-write-this-in-verbatim-latex > > -- > Ihor Radchenko, > Org mode contributor, > Learn more about Org mode at https://orgmode.org/. > Support Org development at https://liberapay.com/org-mode, > or support my work at https://liberapay.com/yantar92 >
Re: [Patch] Pre-/postpend arbitrary LaTeX code to a section
Ihor Radchenko [2022-09-21 Wed 16:55] wrote:
> More concretely, I mean something like
>
> * Section
> :PROPERTIES:
> :attr_latex: :prepend "section" \setcounter{secnumdepth}{0}
> :attr_latex+: :prepend "section"
> \addtocontents{toc}{\protect\setcounter{tocdepth}{0}\ignorespaces}
> :attr_latex+: :append "section" \setcounter{secnumdepth}{2}
> :attr_latex+: :append "section"
> \addtocontents{toc}{\protect\setcounter{tocdepth}{2}\ignorespaces}
> :END:
>
> I suggest to use more canonical attr_latex that explicitly limits the
> export backend.
I don't understand the usecase, that's why I wasn't really following. If
you write \vspace{10cm} before some headline, it's going to do the right
thing even if it "belongs" to a previous headline.
If org-latex-classes is not a good enough solution I also think it should
be a general export feature, not specific to latex. In that case you
need a general syntax, e.g. properties like "export_prefix",
"export_postfix" and the code should be as simple as possible, i.e.
copying the text one line before/after the headline.
--
Daniel Fleischer
Re: Suggested Syntax for cancelled checkboxes: [-] as non-blocking dependency
Karl Voit [2022-09-13 Tue 10:07] wrote: > Is it only me who is thinking that a non-blocking cancelled checkbox > state would be a good idea? At first it makes sense, but we do have headlines and TODO keywords to express different states, colors and even sets of states. This is just a checklist construct. I think if I wanted to mark something as canceled or not relevant I would do something like this: - [ ] this is important. - [X] +canceled+ this is not important. or even strike through everything. I think it's consistent in terms of statistics; you want the total number to represent what you wrote down and what's left does not include the "canceled" tasks. -- Daniel Fleischer
Re: Have all the tags of a heading, with a tag hierarchy
Cletip Cletip [2022-08-28 Sun 18:34] wrote: > I may not have been specific enough: > I want the tags also inherited with this "method" > https://orgmode.org/manual/Tag-Hierarchy.html. I think these are 2 mechanisms that only share the name "hierarchy". One is headline hierarchy: a headline shares the tags of its ancestors. It's local information, it's about the categories this headline are part of because of its location in the document. The other mechanism is for grouping tags into families and is used in the agenda; each family has a representative and you can search for it instead of searching all the individual members. I think it makes sense, but you might want these to be related. -- Daniel Fleischer
Re: [PATCH]: ox-latex: omit empty date
emacs--- via "General discussions about Org-mode."
writes:
> My use case is very niche and be solved by changing my custom latex date
> command by renaming it as for example \mydate.
>
> Adding extra options like with_date:nil seems overkill for this small issue.
I agree; I think we shouldn't change basic behavior for more advanced
usages unless it's something many people are interested in and we keep a
backward compatibility.
> A second option would be is to analyze the data format in the org file.
> If for example the date is specified as
> #+date: {day}{something}
The thing is \date is a macro with one parameter, a string. That's way
\date{} doesn't do anything and \date{\today} prints today's date where
\today return today's date as a string. Starting to introduce new kinds
of inputs - e.g. {y}{m}{d} - to the \date macro would just confuse
people, I think.
Daniel
Re: [PATCH]: ox-latex: omit empty date
Daniel Fleischer [2022-07-31 Sun 18:25] wrote:
> I would reckon people don't want the date displayed when they set it to
> nil. But removing the line \date{} just prints today's date. I don't
> understand the purpose of the patch.
In other words \date{} is what prevents from the date being printed. Or
put differently \date{\today} and not putting \date is equivalent. See
http://www.emerson.emory.edu/services/latex/latex_125.html.
Daniel
Re: [PATCH]: ox-latex: omit empty date
emacs--- via "General discussions about Org-mode." [2022-07-29 Fri 14:49] wrote:
> In the attachment you can find a patch which omits an empty \date{} line in
> a latex document when the option to include the date is set to nil or when
> no date is provided. This empty date line can cause problems is certain
> use cases.
Sorry for the late response.
I would reckon people don't want the date displayed when they set it to
nil. But removing the line \date{} just prints today's date. I don't
understand the purpose of the patch.
Daniel
Re: [PATCH] ob-latex: Added support for including files with a relative path
Ihor Radchenko [2022-07-05 Tue 19:05] wrote:
> Rather than changing paths to absolute, we can simply play with the
> working directly for latex process and set it to the directory of the
> .org file (unless :dir argument is passed to the latex source block).
> This is probably the most expected behavior.
If I understand you correctly, changing the latex processing directory
enables you to use relative paths in macros such as \input{}. If so,
it's as trivial as adding `-cd' flag to `org-latex-pdf-process` when
using `latexmk`.
--
Daniel Fleischer
Re: [PATCH] ob-latex: Added support for including files with a relative path
emacs--- via "General discussions about Org-mode." [2022-07-04 Mon 21:15] wrote: > in the attachment you find a proposed patch to support including external > files > when exporting a latex source block. Currently this was only possible by > using a > :header argument. The problem with this approach is that, files needed to be > included with their absolute path. Hi, adding an "input" type of header is one option. What about adding a call to resolve relative file names instead, thus solving maybe other needs in addition? -- Daniel Fleischer
Re: [PATCH] Re: ox-latex table tabbing support.
Kyle Meyer [2022-06-26 Sun 14:18] wrote: > Thanks for the follow-up patch. > This format doesn't quite align to the conventions. Here are two > examples: > > ,[ https://orgmode.org/worg/org-contribute.html#commit-messages ] > | * lisp/org-capture.el (org-capture-set-plist): Make sure txt is a > | string before calling `string-match'. > | (org-capture-templates): Fix customization type. > ` > > ,[ > https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs > ] > | * lisp/term.el (term-emulate-terminal): Avoid errors if the whole > | decoded string is eight-bit characters. Don't attempt to save the > | string for next iteration in that case. > | * test/lisp/term-tests.el (term-decode-partial) > | (term-undecodable-input): New tests. > ` Thanks for the feedback! Applied to master 321bfb88b5. -- Daniel Fleischer
[PATCH] Re: ox-latex table tabbing support.
Kyle Meyer [2022-06-25 Sat 23:49] wrote:
> Thanks for flagging this, Ihor. I was just glancing at this commit
> (4a0d951c6) due to seeing this warning. It's doing
>
> (let ((align ...))
> (setq align ...))
>
> where the align value is returned, so the align binding can be dropped
> altogether.
>
> Daniel, in addition to that, there are at least a few other issues with
> 4a0d951c6 that should be addressed:
>
> * the first line of the new docstrings should be a complete sentence.
>
>For example
>
> Return an appropriate LaTeX alignment string, for the
> latex tabbing environment.
>
>should be changed to something like
>
> Return alignment string for LaTeX tabbing environment.
>
>See (info "(elisp)Documentation Tips")
>
> * the indentation is off in several places, including the start of the
>docstrings. Please indent the code with, e.g., indent-region.
>
> * one of org-table--org-tabbing's parameters is a typo (contenst),
>which it looks like Ihor pointed out in an earlier review
>
> * comment typo: documets
>
> * several spots put opening and trailing parentheses on their own line
>
>That goes against the usual conventions of this repo:
>
> $ git grep '^ *)' '*.el' | wc -l
> 42
> $ git grep '( *$' '*.el' | wc -l
> 17
>
> * rather than doing something like
>
> (let ((x ""))
>(setq x )
>...)
>
>just do
>
> (let ((x ))
> ...)
>
>And consider whether it's worth adding a binding at all rather than
>inlining the code.
>
>As an extreme case, org-table--org-tabbing does
>
> (let ((output (format ...)))
>output)
>
>rather than
>
> (format ...)
Thanks for the code feedback; patch attached.
>From b041dd62cbeea924ea6d2b6dee9b1142aef968ec Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Sun, 26 Jun 2022 17:25:00 +0300
Subject: [PATCH] lisp/ox-latex.el: tabbing code refactor
* lisp/ox-latex.el: documentation, indentation, cleaning
(org-latex-table)
(org-latex--align-string-tabbing)
(org-table--org-tabbing)
See
https://lists.gnu.org/archive/html/emacs-orgmode/2022-06/msg00700.html.
---
lisp/ox-latex.el | 66 +++-
1 file changed, 31 insertions(+), 35 deletions(-)
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 898fa34dd..1446b7fca 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -3667,7 +3667,8 @@ (defun org-latex-table (table contents info)
((or (string= type "math") (string= type "inline-math"))
(org-latex--math-table table info))
;; Case 3: Tabbing
- ((string= type "tabbing") (org-table--org-tabbing table contents info))
+ ((string= type "tabbing")
+(org-table--org-tabbing table contents info))
;; Case 4: Standard table.
(t (concat (org-latex--org-table table contents info)
;; When there are footnote references within the
@@ -3706,32 +3707,29 @@ (defun org-latex--align-string (table info math?)
(apply 'concat (nreverse align)
(defun org-latex--align-string-tabbing (table info)
-"Return an appropriate LaTeX alignment string, for the
-latex tabbing environment.
+ "Return LaTeX alignment string using tabbing environment.
TABLE is the considered table. INFO is a plist used as
a communication channel."
-(or (org-export-read-attribute :attr_latex table :align)
-(let ((align "")
- (count 0)
- (separator ""))
-;; Count the number of cells in the first row.
-(setq count (length
- (org-element-map
- (org-element-map table 'table-row
-(lambda (row)
- (and (eq (org-element-property :type row) 'standard) row))
-info 'first-match)
- 'table-cell
-(lambda (cell) cell
-;; Calculate the column width, using a proportion of the documets
-;; textwidth.
-(setq separator (format
- "\\hspace{%s\\textwidth} \\= "
- (- (/ 1.0 count) 0.01)))
-(setq align (concat
- (apply 'concat (make-list count separator))
- "\\kill")))
-))
+ (or (org-export-read-attribute :attr_latex table :align)
+ (let* ((count
+ ;; Count the number of cells in the first row.
+ (length
+ (org-element-map
+ (org-element-map table 'table-row
+ (lambda (row)
+ (and (eq (org-element-property
Re: [PATCH] describe how to override Author
Robert Pluim [2022-06-26 Sun 15:47] wrote: > Something like this? (I hope Iʼve got the syntax right, I seldom write > org for exporting purposes). The emacs CONTRIBUTE guidelines talk > about setting 'Author', but I guess not everyone reads those... > +When applying patches written by other people, please ensure that the > +=Author= information of the resulting commit(s) is correct. When > +applying patches created with =git format-patch= this will happen > +automatically, but when applying simple diffs you will need to > +override the author. Here are three ways to do that, depending on 2 spaces here. Looks good and to the point. -- Daniel Fleischer
Re: ox-latex table tabbing support.
Robert Pluim [2022-06-24 Fri 17:01] wrote: > git commit --author='Bob Vergauwen ' > > which would show you as the committer, and Bob as the author. Thanks for the tip; I wasn't aware one can use any identity to author a commit. Perhaps that's why there's an option to do GPG signing in git. Daniel Fleischer
Re: ox-latex table tabbing support.
Robert Pluim [2022-06-24 Fri 15:37] wrote: > Hi Daniel, I see this was committed with you as Author: and Bob as > Created-by:, which is somewhat unusual. I canʼt find anything about > Created-by in the descriptions of org-mode's processes (and this is > the only instance I can see in the commit logs). That patch was actually just a diff, so I created a commit so it was my name. I came up with the "created-by" field to attribute the work to Bob. Is there another way it should have been done? Daniel Fleischer
Re: [PATCH] Improve docstrings of agenda date navigation commands
Stefan Kangas [2022-06-20 Mon 17:54] wrote: > I found the docstrings of the agenda date navigation commands to be somewhat > lacking. The attached patch expands them > slightly and adds crossreferences, which I think makes them much more usable. > Thanks. Thanks, looks good. Merged at e7e37c5b2. Best, -- Daniel Fleischer
Re: ox-latex table tabbing support.
Hi Bob, Thank you very much for the patch. It was merged to master in 4a0d951c. Also, you were added to the orgmode contributes at https://orgmode.org/worg/contributors.html. Thanks for the contribution. Best, -- Daniel Fleischer
Re: [BUG] Cursor is moved after changing list bullets
Ihor Radchenko [2022-06-14 Tue 21:30] wrote: > I am unable to reproduce using any of the supported Emacs versions. > Could you please provide more concrete steps? Or better a test. Create a file called `list.org` with the following: * Test - Hello. - hi. - bye. Then call: emacs -Q -L ./Projects/org-mode/lisp/ -l org list.org Then put the cursor on one of the hyphens and change its style using S-right. The bullet will change and the cursor will move to the beginning of a word instead of stay in place. -- Daniel Fleischer
[BUG] Cursor is moved after changing list bullets
Hi, there is a regression introduced in: ed6f8dc67 org-list: Do not move point and change space when promoting/demoting items When calling `org-cycle-list-bullet' (e.g. using S-right or S-left) the cursor moves to the beginning of the text after changing the bullet type. It used to not move which is useful to when trying different bullet styles. This is due to the changes in `org-list-struct-apply-struct'. I tried to debug it but I'm not sure what was the issue the patch was meant to solve. Thanks, -- Daniel Fleischer
Re: [PATCH] Don't quote symbols in defcustom types
Thanks for the patch, merged. Daniel Fleischer
Re: [PATCH] Don't quote symbols in defcustom types
Robert Pluim [2022-06-14 Tue 11:28] wrote: > A couple of places in org main quoted symbols in defcustom types, but > the type itself is already quoted, so thatʼs not necessary. Is it harmful though? > - (const :tag "Overlays" 'overlays) > - (const :tag "Text properties" 'text-properties))) > + (const :tag "Overlays" overlays) > + (cnost :tag "Text properties" text-properties))) Typo here `cnost`. -- Daniel Fleischer
Re: Org default is Left-to-right
Ihor Radchenko [2022-06-14 Tue 13:17] wrote: > The Emacs devs reply was that 'right-to-left global setting is preferred > for such users while nil being preferred setting for other users and it > should not be something Org decides. > > Hence, I just applied a patch removing Org setting > bidi-paragraph-direction to main (0cdbc63a0). The right-to-left setting makes everything RTL, and more often than not I have mixed-languages documents which looks better with nil direction value. Anyways, good judgment; it is up to a user who uses different languages to decide how Emacs should align the text and it should carry naturally into Org. -- Daniel Fleischer
Re: [PATCH] New remote resource download policy
Timothy [2022-06-12 Sun 22:43] wrote: > As was raised in the #+include: URL thread > (https://list.orgmode.org/877d5sd7yu@gmail.com), currently Org will > automatically download files without confirmation in various circumstances. > > This patch introduces two variables to control Org’s attitude towards > downloading files, and hooks them into the > relevant parts of the codebase. Hi Timothy, looks very nice! I was also bothered by it, specifically in the case of #+setupfile. Having a safe URI regexp list is a nice addition, similar to `org-link-elisp-skip-confirm-regexp'. I'll definitely give it a try. -- Daniel Fleischer
Re: [PATCH] org.el (org-latex-preview): With an active region, act on it
Sébastien Miquel writes: > Thanks for your comment and testing this. > > Note that I do not have merge access to the repository. OK, I merged it now. Thanks for the contribution! -- Daniel Fleischer
Re: [PATCH] org.el (org-latex-preview): With an active region, act on it
Sébastien Miquel [2022-06-08 Wed 11:35] wrote: > The attached patch modifies org-latex-preview to display all images > of latex fragments in a region, when one is active. > Using prefix arguments it is already possible to display all images > in the buffer, or in the current section, but I find it often too slow > and unnecessary. Hi Miquel, thanks for the patch! It's useful and works nicely - both in creating and removing the previews. Let's give it a couple more days for feedback and then feel free to merge the patch. Thanks, -- Daniel Fleischer
Re: [PATCH] manual: fix variable name
Thanks, merged. -- Daniel Fleischer
Re: [PATCH] Avoid ignoring LaTeX export output errors when org-latex-pdf-process is a list
Ihor Radchenko [2022-05-22 Sun 11:51] wrote: > The attached patch is fixing a rather annoying problem when > org-latex-pdf-process is set to a list. Currently, only output of the > last command in the list is preserved in *Org PDF LaTeX output* buffer, > which sometimes prevents ox-latex from detecting compilation warnings. > ox-latex relies on *Org PDF LaTeX output* to contain the output of latex > compiler. However, unless the last command in the org-latex-pdf-process > is something like pdflatex, the compiler errors are erased by > `shell-command' called by `org-compile-file'. Looks good. So the log buffer is going to be a concatenation of all the logs. Will ox-latex parse the longer log in a meaningful way? Is it just for the user to find issues by herself after a failed compilation? Daniel Fleischer
Re: [BUG] HTML export of buffer with fringe indicators
Ihor Radchenko [2022-05-20 Fri 16:36] wrote: > I am unable to reproduce your problem on my side using the following > steps. Ok, thanks anyway. BTW, even the steps you took are useful for me for future debugging. Best, Daniel Fleischer
Re: [BUG] HTML export of buffer with fringe indicators
Ihor Radchenko [2022-05-19 Thu 21:43] wrote: > What if you try to run M-: (htmlize-buffer) > on your file? It works, creating an HTML buffer that can be opened and looks good. -- Daniel Fleischer
Re: [BUG] HTML export of buffer with fringe indicators
g-html-entity) (example-block . org-html-example-block) (export-block . org-html-export-block) (export-snippet . org-html-export-snippet) (fixed-width . org-html-fixed-width) (footnote-reference . org-html-footnote-reference) (headline . org-html-headline) (horizontal-rule . org-html-horizontal-rule) (inline-src-block . org-html-inline-src-block) (inlinetask . org-html-inlinetask) (inner-template . org-html-inner-template) (italic . org-html-italic) (item . org-html-item) (keyword . org-html-keyword) (latex-environment . org-html-latex-environment) (latex-fragment . org-html-latex-fragment) (line-break . org-html-line-break) (link . org-html-link) (node-property . org-html-node-property) (paragraph . org-html-paragraph) ...) :exported-data # :input-buffer "כתיבה.txt" :input-file "/Users/danielfleischer/Doc..." :html-doctype "xhtml-strict" :html-container "div" :html-content-class "content" :description nil :keywords nil :html-html5-fancy t :html-link-use-abs-url nil ...)) org-export-as(html t nil nil (:output-file "כתיבה.html")) org-export-to-file(html "כתיבה.html" nil t nil nil nil) org-html-export-to-html(nil t nil nil) (org-open-file (org-html-export-to-html nil s v b)) (if a (org-html-export-to-html t s v b) (org-open-file (org-html-export-to-html nil s v b))) (lambda (a s v b) (if a (org-html-export-to-html t s v b) (org-open-file (org-html-export-to-html nil s v b(nil t nil nil) org-export-dispatch(nil) funcall-interactively(org-export-dispatch nil) command-execute(org-export-dispatch) Thanks, -- Daniel Fleischer
[BUG] HTML export of buffer with fringe indicators
The case I have in mind is some code with folding indicators in the fringe. E.g. have this python block: #+begin_src python def hi(): pass #+end_src Have `elpy' installed with enabled fringe markers (have `elpy-folding-fringe-indicators' non-nil). Then try to export, say to HTML. I get the error cons: Args out of range: " ", 0, -3 Org cdbb1c9633. Emacs eaa198cd75. Thanks, -- Daniel Fleischer
Re: [PATCH] (v3) New LaTeX code export option: engraved
Looks good. I had to update `engrave-faces' to 0.3 because of new variables/functions and it works now. It does what it says on the box so let's move forward introducing these changes and be open to feedback. Thank you very much for introducing this feature! -- Daniel Fleischer
Re: Org-ref not working when exporting to LaTeX
John Kitchin [2022-05-11 Wed 14:17] wrote: > The regular export is preferred for LaTeX (C-c C-e l o) is preferred for > LaTeX export as it generates the LaTeX cite > commands. The version in C-c C-e r p uses CSL for the formatting, not LaTeX, > and it allows you to get nicely formatted > results without using bibtex/biblatex as the citation processor. Oops! Thanks for correcting my answer and mentioning the difference between the CSL and bibtex engines. -- Daniel Fleischer
Re: Regarding arbitrary Org blocks
Russell Adams [2022-05-11 Wed 18:14] wrote: > Could I add some minor mode to say text-mode with auto-fill-mode and > aspell somewhere when opening those blocks? Hi! If you're editing text why do you need a special buffer? You can edit them in the orgmode buffer and enjoy all its textual features. The special buffer is for major modes which are not orgmode such as programming languages or latex which use different completions/highlighting/minor-modes and editing them in orgmode is a hassle. -- Daniel Fleischer
Re: Org-ref not working when exporting to LaTeX
Alessandro Bertulli [2022-05-11 Wed 19:41] wrote: > I'm going to post my setup in a minute. The > point is: when exporting the org file to LaTeX (C-c C-e l o), a PDF file > gets produced, but it doesn't process the citation keys. For example, in > my file (see below), I got the key "acm:code" literally printed on the > PDF file, in a bold font. Hi, org-ref uses its own export engine which you call via (C-c C-e r p). Please try that and report back if there are still issues. -- Daniel Fleischer
Re: Recent changes in org-fold regarding emphasize visibility
Ihor Radchenko writes: > I have made changes in invisible edit handling. > Now, when using 'text-properties style, > org-fold-check-before-invisible-edits ignores folded links just like it > does with overlays style. > > The commit is 2e4ed52b1. Looks good; thank you Ihor! -- Daniel Fleischer
Re: [PATCH] New LaTeX code export option: engraved
Hi Timothy, Very nice set of patches, it looks good. Listings and minted are still workable options and your new engrave library is available. I must admit it's not clear how to customize faces since engrave is a bridge between major modes choices and latex but maybe show one or two examples (say elisp and python) of how to change/override some face. I think next we should apply these patches and be open to feedback about source code latex export using these new changes. I also wish there was a bit more documentation, but we can add more with time. Maybe some feedback from Nicolas G.? Best, -- Daniel Fleischer
Re: Recent changes in org-fold regarding emphasize visibility
Ihor Radchenko [2022-05-07 Sat 12:22] wrote: > Now, we have different kinds of hidden text at hand: > - folded headlines/lists > - folded drawers > - folded blocks > - folded links/emphasis > > The question is what should be the logical behaviour of Org when editing > text inside or at the border of these hidden text types? How should we > interpret the values of org-catch-invisible-edits (nil error show > show-and-error smart)? Hi Ihor, Not sure we need to reinterpret the settings; roughly they cover the different options of what to do when you edit a hidden text: edit anyways, throw an error, unfold but do nothing, unfold and do what you wanted to do and the only thing I don't have an intuition about is the smart option. BTW, there are no issues when the folding core style is "overlays". So why not follow what happens in that case, even formalize it into tests? Best, -- Daniel Fleischer
Re: Recent changes in org-fold regarding emphasize visibility
Ihor Radchenko writes: > Fixed on main by d2a459d25 I've tried the commit. I think there are still issues. E.g. given a folded headline * Introduction...| * Section Inserting text at that point will do the following thing depending on `org-fold-catch-invisible-edits': - error : it inserts the text without unfolding; most dangerous. - show : unfold, insert the text without displaying it; dangerous. - show-and-error: unfold but inserts the text anyways. Thanks, -- Daniel Fleischer
Re: [PATCH] New LaTeX code export option: engraved
Timothy [2022-05-04 Wed 23:59] wrote: > I’ve been fairly busy as of late (hence my recent silence on this ML), > however I have a patchset that’s been in the > works for a while that I’ve finally polished up. Hi Timothy, thank you very much for your work! Let me learn a bit about the different code highlighting options in order to understand what you offer. Best, -- Daniel Fleischer
Re: [PATCH] New LaTeX code export option: engraved
Timothy [2022-05-04 Wed 23:59] wrote: > I’ve been fairly busy as of late (hence my recent silence on this ML), > however I have a patchset that’s been in the > works for a while that I’ve finally polished up. Hi Timothy, thank you very much for your work! Let me learn a bit about the different code highlighting options in order to understand what you offer. Best, -- Daniel Fleischer
Recent changes in org-fold regarding emphasize visibility
There are some recent (week old) changes to org-fold that changes fold/emphasize behavior. Before the changes, I used to have (setq org-fold-catch-invisible-edits 'show-and-error) in order to prevent accidental write in the following places: :PROPERTIES:|... But now, hidden emphasize symbols are considered "folded" so when I write: *Hello*| and about to press "space" I get a warning. I think this is a regression. I don't want to change the `org-fold-catch-invisible-edits' variable to something else because I worry more about accidental edits in real folded regions. I don't understand why emphasize markers are treated as folded text. `org-hide-emphasis-markers` is set to non-nil. Best, -- Daniel Fleischer
Re: How to export to markdown programmatically without the table of contents?
Karl Voit writes: > Could it be that I don't have "md" as backend somehow? Is there a > hidden requirement? The variable `org-export-backends` default value is '(ascii html icalendar latex odt) so you need to add 'md. -- Daniel Fleischer
Re: [BUG] - Statistics cookie is part of the org heading title
Fabian writes: > I don't see any reason why the statistics cookie should be part of the title: > it should be a separate component. According to the spec, the statistics cookie can appear anywhere, it's a text element. It can appear in a headline where it has more meaning and also appear anywhere in the headline, not necessarily at the end. The function you failed to mention but is mentioned in the link is `org-heading-components` which does a simple split around syntax parts: stars, TODO word, text, tags. If you don't want to see the cookie you can remove it easily from text using regex. -- Daniel Fleischer
Re: How to export to markdown programmatically without the table of contents?
Jeremie Juste [2022-05-01 Sun 22:29] wrote: > I know where to look now: > > (info "(org) Publishing options") That's a good resource!
Re: [tip] Org speed commands improved
Juan Manuel Macías [2022-04-26 Tue 14:00] wrote: > Org speed commands are a major productivity boost and I love them. > Lately it has occurred to me to make some modifications with the > following configuration, which I share here in case someone wants to try > it. The idea is that Org speed commands are activated anywhere in the > header (not just at the beginning of the line) *or* when point is at the > very beginning of the buffer. This, in my opinion, improves the > navigation speed: Very nice idea; I'll give it a try, thanks! -- Daniel Fleischer
Re: Maintenance Request
Edouard Debry [2022-04-21 Thu 00:58] wrote: > Thanks for offering to maintain 'ox-latex.el'. > > One of the thing that could be improved is the generation of svg > images through tikz. Currently, unless I am mistaken, it does > not work well. I had to tweak 'ox-latex.el' to make it work again. > I did post a question about this on the mailing list. > I'll try to find the question. Would you like to submit a patch based on your modifications?
Re: Feedback on Emacs-Jupyter
Hi, I submitted an issue regarding connection file format incompatibility. Other than that I'm looking forward trying your package! -- Daniel Fleischer
Re: How to add font-lock keywords
Bruno Barbier [2021-12-21 Tue 20:35] wrote:
> The following works for me, in an org mode buffer:
>
> ,
> | (font-lock-add-keywords nil '(("books" . 'org-level-4)) t)
> `
> No need to call font-lock-update or restart: any new or modified text
> gets the new fontification.
Thanks, it works with the quote.
--
Daniel Fleischer
How to add font-lock keywords
Hi, I want to add custom keywords to be highlighted. I used
(font-lock-add-keywords nil '(("books" . org-level-4)) t)
but nothing happens after I restart orgmode or call 'font-lock-update'.
--
Daniel Fleischer
Re: Org Mode "Contribute", "Maintenance" pages don't give repository.
Karl Fogel writes:
> The reason I suggest this is that often when someone is hot on the trail of
> debugging something, they haven't yet
> decided whether they want to become a contributor or not. They just know
> they want to ook at the latest sources so they
> can first figure out more about whatever ${technical_thing} they encountered.
> So making the latest sources very easy to
> find is a way of making it more likely that someone becomes a contributor, by
> removing a commonly-encountered barrier.
You're right; I'll think of a way to present the git repo link, i.e. the
code earlier and more prominently for those who just want to jump and
examine the code.
--
Daniel Fleischer
Re: Org Mode "Contribute", "Maintenance" pages don't give repository.
Karl Fogel [2021-12-04 Sat 14:59] wrote: > The "Contribute" page at https://orgmode.org/worg/org-contribute.html does > not mention > git://git.sv.gnu.org/emacs/org-mode.git . Actually, now that I look around, > the "Maintenance" page at > https://orgmode.org/worg/org-maintenance.html doesn't mention the repository > address either. It does mention the word > "repository" a few times, but never actually links to it. I've added a link to the org-maintenance page but there was a link in the org-contribute, in the "Your first commit as an Org maintainer" section. The git.sv.gnu.org is a shorthand for git.savannah.gnu.org. Thanks for reporting this, -- Daniel Fleischer
Maintenance Request
Hi all, I would like to maintain the 'ox-latex.el' file. It's one of the many files created by Nicolas but few of the files that are not maintained (by him). I have a long experience (14) with latex and relatively long experience with org->latex. Best, -- Daniel Fleischer
Re: [BUG] org-mode binds C-c C-TAB, which seems illegal [9.5 (9.5-g0a86ad @ /home/il/.config/emacs/elpa/org-9.5/)]
Ingo Lohmar [2021-11-17 Wed 21:19] wrote: > Can people actually enter "C-c C-TAB" into their emacs (how?), or has > everybody has just bound another key in their config? I've noticed it a couple of weeks ago; just rebound org-force-cycle-archived to (kbd "C-c C-") -- Daniel Fleischer
Re: Org default is Left-to-right
Ihor Radchenko writes: > See https://lists.gnu.org/archive/html/emacs-devel/2011-09/msg00285.html OK, so 10 years ago on Emacs 24 it might have caused some slowdown on large Org files. It wasn't clear if these people needed RTL or not, because I set it to nil as soon as I open my Org files. I guess I'll use a hook in my config. You could also turn it back to nil and see if people complain, as part of 9.6. -- Daniel Fleischer
Org default is Left-to-right
Hi, in org.el , when defining the mode there's the code (setq bidi-paragraph-direction 'left-to-right) which makes everything left-to-right instead of 'nil which smartly aligns paragraphs either LTR or RTL according to the language of that paragraph. nil is Emacs default. I don't understand why Org chooses to align everything to the left, disregarding any RTL language. Org works great with RTL and even with mixed languages, as many people can attest. Can we consider dropping this line? LTR people wouldn't notice any difference but RTL people will appreciate it without needing to override it using a hook or toggling it with some elisp code (like I did). Thanks, -- Daniel Fleischer
[PATCH] Fast tag de-selection face
Bumping a patch; it solves a minor bug in which the tags in the fast tag selection buffer do not toggle their face back to default after being selected and deselected. Attached. >From 50fd7e953eed7c339886722c8247d9e492113eb8 Mon Sep 17 00:00:00 2001 From: Daniel Fleischer Date: Fri, 8 Oct 2021 12:55:04 +0300 Subject: [PATCH] lisp/org.el: Fast tag selection disabled tag face * lisp/org.el (org-fast-tag-selection): Disabled tags face A tag can be either selected in "current", "inherited" or disabled. When disabled, it should have the default face. Previously, if a tag was already selected, when deselection it will still have an org-todo face. --- lisp/org.el | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 21b2c5470..bcc8356bb 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -12566,8 +12566,7 @@ (defun org-fast-tag-selection (current inherited table todo-table) (cond ((member tag current) c-face) ((member tag inherited) i-face) -(t (get-text-property (match-beginning 1) ' - face +(t 'default))) (goto-char (point-min) (delete-overlay org-tags-overlay) (if rtn -- 2.33.1 -- Daniel Fleischer
Re: MathJax extension does not work
Daniel Fleischer writes: > Not sure why the "#+HTML_MATHJAX: mathtools.js" doesn't do anything. > Need further investigation. After examining the function 'org-html--build-mathjax-config' in 'ox-html.el' and also looking at the default values of - 'org-html-mathjax-options' - 'org-html-mathjax-template' I don't see any code that loads mathjax extensions; which means the documentation in https://orgmode.org/manual/Math-formatting-in-HTML-export.html is not accurate. That's my understanding. -- Daniel Fleischer
Re: MathJax extension does not work
Rudolf Adamkovič writes:
> I would like to use the "\mathclap" command from the "mathtools" package in
> my Org document. In LaTeX, it works. For
Hi, there are 2 problems: first the mathtools.js library was introduced in
mathjax 3.2 but org provided version 2.7 as can be seen in the HTML
#+begin_src html
https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0/MathJax.js?config=TeX-AMS_HTML"</a>;>
#+end_src
One can use the newer mathjax by replacing this with
#+begin_src html
https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js"</a>;>
#+end_src
as seen in https://docs.mathjax.org/en/latest/web/start.html.
You can just change the "path" in 'org-html-mathjax-options'.
Secondly, mathtools is not autoloaded so you need to call it; for
example you can put it in org using "export" block.
#+begin_src HTML
window.MathJax = {
loader: {load: ['[tex]/mathtools']},
tex: {packages: {'[+]': ['mathtools']}}
};
#+end_src
After that it worked.
Not sure why the "#+HTML_MATHJAX: mathtools.js" doesn't do anything.
Need further investigation.
--
Daniel Fleischer
Re: [PATCH] Bug: Tag Selection Face Doesn't Toggle
> Daniel Fleischer writes: > >> Hi, when selecting tags using fast selection and then de-selecting, the >> face doesn't toggle back to regular face. >> It's better to have a default face instead of 'org-default face. >From f269d3ad99b8ad570c19961831f38653046f07fb Mon Sep 17 00:00:00 2001 From: Daniel Fleischer Date: Fri, 8 Oct 2021 12:55:04 +0300 Subject: [PATCH] lisp/org.el: fast tag selection disabled tag face A tag can be either selected in "current", "inherited" or disabled. When disabled, it should have the 'org-default face. Previously, if a tag was already selected, upon deselection it will still have an 'org-todo face. --- lisp/org.el | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 18cb53af6..1dfe70735 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -12440,8 +12440,7 @@ (defun org-fast-tag-selection (current inherited table todo-table) (cond ((member tag current) c-face) ((member tag inherited) i-face) -(t (get-text-property (match-beginning 1) ' - face +(t 'default))) (goto-char (point-min) (delete-overlay org-tags-overlay) (if rtn -- 2.33.0
[PATCH] Bug: Tag Selection Face Doesn't Toggle
Daniel Fleischer writes: > Hi, when selecting tags using fast selection and then de-selecting, the > face doesn't toggle back to regular face. > > Fast selection means `org-use-fast-tag-selection' is t. See attached. >From 0352757d7012dc543bae4039deaed7bbd401bb9f Mon Sep 17 00:00:00 2001 From: Daniel Fleischer Date: Fri, 8 Oct 2021 12:55:04 +0300 Subject: [PATCH] lisp/org.el: fast tag selection disabled tag face A tag can be either selected in "current", "inherited" or disabled. When disabled, it should have the 'org-default face. Previously, if a tag was already selected, upon deselection it will still have an 'org-todo face. --- lisp/org.el | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 18cb53af6..e6a0350c1 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -12440,8 +12440,7 @@ (defun org-fast-tag-selection (current inherited table todo-table) (cond ((member tag current) c-face) ((member tag inherited) i-face) -(t (get-text-property (match-beginning 1) ' - face +(t 'org-default))) (goto-char (point-min) (delete-overlay org-tags-overlay) (if rtn -- 2.33.0 -- Daniel Fleischer
Re: Maintainer Duties
Daniel Fleischer [2021-10-06 Wed 18:05] wrote: > Only 30 out of the 122 Elisp files have a maintainer. I'm interested in > maintaining one or more files but I'm not sure what it means. Can we > make it clearer, as perhaps other people are interested and want to > know. Thanks Bastien for documenting a good explanation of the role; for reference, see section "What is the role of a maintainer?" in https://orgmode.org/worg/org-maintenance.html. -- Daniel Fleischer
Maintainer Duties
Hi all, Only 30 out of the 122 Elisp files have a maintainer. I'm interested in maintaining one or more files but I'm not sure what it means. Can we make it clearer, as perhaps other people are interested and want to know. Here are some possible aspects of the role: 1. Actively improve the file content: function documentation, error handling, formatting, notation (syntax). 2. Identify messages in the mailing list related to the file. Participate in these threads. 3. Become an expert on the functionality in the file. 4. Offer new functionality, features, improve existing code (semantics). 5. Review all patches related to the file and then approve them or order a rework. Finally, merge them. Or maybe some other aspects? Thanks, -- Daniel Fleischer
Bug: Tag Selection Face Doesn't Toggle
Hi, when selecting tags using fast selection and then de-selecting, the face doesn't toggle back to regular face. Fast selection means `org-use-fast-tag-selection' is t. Checked with emacs -Q + (setq org-use-fast-tag-selection t). Org 9.5, commit cc2490a7061955395c4f5a1a23a088044554a2f7. Emacs 29.0.50, hash 9f041cdfaca0f3def74eb7d3348bbf35c12bcc5b. -- Daniel Fleischer
Re: Some broken links in pages under https://orgmode.org/worg/org-contrib/babel
> Mandar Mitra [2021-10-04 Mon 18:15] wrote: > >> * https://orgmode.org/worg/org-contrib/babel/intro.html >> *** ... relevant section in the >> [[https://orgmode.org/manual/Literal-examples.html][Org manual]] ... >> *** please have a look at the >> [[https://orgmode.org/manual/Literal-examples.html][Org-mode manual]] before >> proceeding >> *** blocks located in the >> [[https://orgmode.org/worg/org-contrib/babel/library-of-babel.html][Library >> of Babel]] file – raw file at >> >> * https://orgmode.org/worg/org-contrib/babel/uses.html >> *** >> [[https://orgmode.org/worg/org-contrib/babel/examples/org-check.html][Checking >> Your Org Mode Configuration]] >> *** >> [[https://orgmode.org/worg/org-contrib/babel/examples/data-collection-analysis.html][Data >> Collection and Analysis]] Pushed a fix for 2 HTML links fixes. Pushed a fix for "data-collection-analysis". - "org-check" needs refactor of the latex section in order to compile. - "org-contrib/babel/library-of-babel" not sure why it doesn't appear on the server because the file compiles locally to HTML. -- Daniel Fleischer
Re: Some broken links in pages under https://orgmode.org/worg/org-contrib/babel
Mandar Mitra [2021-10-04 Mon 18:15] wrote: Confirmed 5 Broken links: > * https://orgmode.org/worg/org-contrib/babel/intro.html > *** ... relevant section in the > [[https://orgmode.org/manual/Literal-examples.html][Org manual]] ... > *** please have a look at the > [[https://orgmode.org/manual/Literal-examples.html][Org-mode manual]] before > proceeding > *** blocks located in the > [[https://orgmode.org/worg/org-contrib/babel/library-of-babel.html][Library > of Babel]] file – raw file at > > * https://orgmode.org/worg/org-contrib/babel/uses.html > *** > [[https://orgmode.org/worg/org-contrib/babel/examples/org-check.html][Checking > Your Org Mode Configuration]] > *** > [[https://orgmode.org/worg/org-contrib/babel/examples/data-collection-analysis.html][Data > Collection and Analysis]] -- Daniel Fleischer
Debbugs Usage
Hi, is debbugs org-mode being used? -- Daniel Fleischer
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Joseph Vidal-Rosset writes: > To capture an email and to link this message for gnus, I get now this > error message: > > Capture abort: Symbol’s function definition is void: turn-on-org-provide What is your capture template? -- Daniel Fleischer
bug#50555: [PATCH] Re: bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Younes Ben El writes:
> Daniel Fleischer writes:
>
> Here is the hint: since “minted” is using a python package (pygments) for
> the highlighting, one need to add the
> “-shell-escape” to the call. Other than that, everything works as
> planned. Since it’s a specific configuration for
> using “minted”, I’ll add a comment in the manual.
>
> If you feel that there is still an issue with the [], please provide an
> emacs -Q recipe that shows it, after adding
> the “-shell-escape” flag.
>
> Ah, That’s the deal. Updating The Manual Will do the trick Thanks for taking
> time and looking up at this issue .
>
Patch: comment suggesting the usage of the flag; many changes due to the
footnote numbering "push".
>From 64150d05e83b346969173134cbd237cc3aae7e15 Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Sat, 18 Sep 2021 22:57:32 +0300
Subject: [PATCH] org-manual: comment about latex code-block export
* doc/org-manual.org: when using the latex Minted package, one needs to
set the '-shell-escape' flag in 'org-latex-pdf-process'.
Signed-off-by: Daniel Fleischer
---
doc/org-manual.org | 112 +++--
1 file changed, 58 insertions(+), 54 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 10813a812..9776abb76 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -13769,7 +13769,7 @@ *** Source blocks in LaTeX export
The LaTeX export back-end passes string values in =:options= to LaTeX
packages for customization of that specific source block. In the
example below, the =:options= are set for Minted. Minted is a source
-code highlighting LaTeX package with many configurable options.
+code highlighting LaTeX package with many configurable options[fn:134].
#+begin_example
,#+ATTR_LATEX: :options commentstyle=\bfseries
@@ -14021,7 +14021,7 @@ ** OpenDocument Text Export
The ODT export back-end handles creating of OpenDocument Text (ODT)
format. Documents created by this exporter use the
-{{{cite(OpenDocument-v1.2 specification)}}}[fn:134] and are compatible
+{{{cite(OpenDocument-v1.2 specification)}}}[fn:135] and are compatible
with LibreOffice 3.4.
*** Pre-requisites for ODT export
@@ -14422,7 +14422,7 @@ LaTeX math snippets
variables ~org-latex-to-mathml-convert-command~ and
~org-latex-to-mathml-jar-file~.
- If you prefer to use MathToWeb[fn:135] as your converter, you can
+ If you prefer to use MathToWeb[fn:136] as your converter, you can
configure the above variables as shown below.
#+begin_src emacs-lisp
@@ -14433,7 +14433,7 @@ LaTeX math snippets
#+end_src
#+texinfo: @noindent
- or, to use LaTeXML[fn:136] instead,
+ or, to use LaTeXML[fn:137] instead,
#+begin_src emacs-lisp
(setq org-latex-to-mathml-convert-command
@@ -14752,7 +14752,7 @@ Customizing tables in ODT export
tables, see [[*Tables in ODT export]].
This feature closely mimics the way table templates are defined in the
-OpenDocument-v1.2 specification[fn:137].
+OpenDocument-v1.2 specification[fn:138].
#+vindex: org-odt-table-styles
For quick preview of this feature, install the settings below and export the
@@ -14786,7 +14786,7 @@ Customizing tables in ODT export
To use this feature proceed as follows:
-1. Create a table template[fn:138].
+1. Create a table template[fn:139].
A table template is set of =table-cell= and =paragraph= styles for
each of the following table cell categories:
@@ -14825,7 +14825,7 @@ Customizing tables in ODT export
== element of the content template file
(see [[x-orgodtcontenttemplate-xml][Factory styles]]).
-2. Define a table style[fn:139].
+2. Define a table style[fn:140].
#+vindex: org-odt-table-styles
To define a table style, create an entry for the style in the
@@ -15939,7 +15939,7 @@ *** Publishing action
~org-org-publish-to-org~. This produces =file.org= and puts it in the
publishing directory. If you want a htmlized version of this file,
set the parameter ~:htmlized-source~ to ~t~. It produces
-=file.org.html= in the publishing directory[fn:140].
+=file.org.html= in the publishing directory[fn:141].
Other files like images only need to be copied to the publishing
destination; for this you can use ~org-publish-attachment~. For
@@ -17322,13 +17322,13 @@ *** How to evaluate source code
#+kindex: C-c C-v e
#+findex: org-babel-execute-src-block
Org provides many ways to execute code blocks. {{{kbd(C-c C-c)}}} or
-{{{kbd(C-c C-v e)}}} with the point on a code block[fn:141] calls the
+{{{kbd(C-c C-v e)}}} with the point on a code block[fn:142] calls the
~org-babel-execute-src-block~ function, which executes the code in the
block, collects the results, and inserts them in the buffer.
#+cindex: @samp{CALL}, keyword
#+vindex: org-babel-inline-result-wrap
-By calling a named code block[fn:142] from an Org mode buffer or
+By
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
I verified again, this time with emacs -Q; the empty argument list []
does NOT stop you from compiling org into PDF.
> (with-eval-after-load 'ox-latex
> (add-to-list 'org-latex-packages-alist '("" "minted"))
> (setq org-latex-listings 'minted)
> (setq org-latex-pdf-process
> '("pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f")))
>
Here is the hint: since "minted" is using a python package (pygments) for
the highlighting, one need to add the "-shell-escape" to the call. Other
than that, everything works as planned. Since it's a specific
configuration for using "minted", I'll add a comment in the manual.
If you feel that there is still an issue with the [], please provide an
emacs -Q recipe that shows it, after adding the "-shell-escape" flag.
--
Daniel Fleischer
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Younes Ben El [2021-09-12 Sun 21:25] wrote: > When exporting from org to latex , src blocks are not handled correctly. > This happens when you specify a prog-language name after #+BEGIN_SRC > Which results to an extra *[]* in exported latex file thus when > compiling it to pdf , it won't display the code block. It's true that there are empty [] argument list for the minted package in the latex code; however I am able to compile your (and my) latex code into PDF with and without it so I'm not sure that something needs to be done in org-mode. Can you send the resulting latex file and/or specify why it's not compiling? -- Daniel Fleischer
Re: [PATCH] Re: [BUG] Creating sparse tree with regexp property matches
Timothy writes: > Thanks for bumping your patch, unfortunately many of us (people who can push > to > Org) seem to be stretched a bit thin as of late. I’ve just gone over it, it > reads well IMO and I think looking at the non-trivial changes in your patch > it’s > possible to charitably interpret this as <=15 non-trivial lines changed. I’ve > applied this as 6600dc09 on Org master with a tweaked commit message . > > Documentation is vital to communicating what Org offers to users, so thanks > again for going to the effort to clear up a possible point of confusion. > Should > you wish to make any further contributions (which would be great!) it would be > very helpful if you could get FSF assignment (see > <https://orgmode.org/contribute.html>), as we can’t accept more than 15 lines > of > non-trivial lines as an FSF project. Thanks Timothy for pushing this. I just received my FSF assignment so looking forward to contributing more. Best, -- Daniel Fleischer
Re: [PATCH] Re: [BUG] Creating sparse tree with regexp property matches
> Attached is a patch with improvement to documentation regarding regular > expressions. Hi, how do I get the patch approved/committed to org? -- Daniel Fleischer
Re: [BUG?] org-agenda not showing entries with diary sexp timestamps
Eric S Fraga [2021-09-10 Fri 11:57] wrote: > What works for me, for diary sexp entries, is putting the time in the > heading: > > * 09:00-10:00 Weekly meeting > <%%(diary-cyclic 7 9 10 2021)> This is exactly how the feature is described in the manual: #+begin_example Diary-style expression entries For more complex date specifications, Org mode supports using the special expression diary entries implemented in the Emacs Calendar package(2). For example, with optional time: * 22:00-23:00 The nerd meeting on every 2nd Thursday of the month <%%(diary-float t 4 2)> #+end_example -- Daniel Fleischer
Re: [BUG?] org-agenda not showing entries with diary sexp timestamps
Eric S Fraga writes: > What works for me, for diary sexp entries, is putting the time in the > heading: > > * 09:00-10:00 Weekly meeting > <%%(diary-cyclic 7 9 10 2021)> Actually, that is how the manual explain their usage. [[info:org#Timestamps]] -- Daniel Fleischer
Re: [BUG?] org-agenda not showing entries with diary sexp timestamps
Yuchen Pei [2021-09-10 Fri 18:00] wrote: > * Weekly meeting > <%%(diary-cyclic 7 9 10 2021) 9:00-10:00> > > Invoking org-agenda with a (org-agenda-list) does not show the item, whereas > scheduled diary sexp or plain timestamp > works fine: > > * Weekly meeting > SCHEDULED: <%%(diary-cyclic 7 9 10 2021) 9:00-10:00> > I can reproduce; adding the hour makes the event not appear unless it has a DEADLINE or SCHEDULED. -- Daniel Fleischer
[PATCH] Re: [BUG] Creating sparse tree with regexp property matches
Attached is a patch with improvement to documentation regarding regular
expressions.
Best,
Daniel Fleischer
>From d3d1dcbc5f62ea111e7bcd1741114cae6b1280c5 Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Tue, 31 Aug 2021 20:01:47 +0300
Subject: [PATCH] org-manual: added section about regular expressions
Telling users it's based on Elisp regular expressions, linking to its
info node and putting some links to this new node in places where regexp
are presented.
Signed-off-by: Daniel Fleischer
---
doc/org-manual.org | 80 --
1 file changed, 49 insertions(+), 31 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 10e0baa28..02eaa10f2 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -916,16 +916,16 @@ ** Sparse Trees
#+kindex: C-c / /
#+findex: org-occur
#+vindex: org-remove-highlights-with-change
- Prompts for a regexp and shows a sparse tree with all matches. If
- the match is in a headline, the headline is made visible. If the
- match is in the body of an entry, headline and body are made
- visible. In order to provide minimal context, also the full
- hierarchy of headlines above the match is shown, as well as the
- headline following the match. Each match is also highlighted; the
- highlights disappear when the buffer is changed by an editing
- command, or by pressing {{{kbd(C-c C-c)}}}[fn:8]. When called with
- a {{{kbd(C-u)}}} prefix argument, previous highlights are kept, so
- several calls to this command can be stacked.
+ Prompts for a regexp (see [[*Regular Expressions]]) and shows a sparse
+ tree with all matches. If the match is in a headline, the headline
+ is made visible. If the match is in the body of an entry, headline
+ and body are made visible. In order to provide minimal context,
+ also the full hierarchy of headlines above the match is shown, as
+ well as the headline following the match. Each match is also
+ highlighted; the highlights disappear when the buffer is changed by
+ an editing command, or by pressing {{{kbd(C-c C-c)}}}[fn:8]. When
+ called with a {{{kbd(C-u)}}} prefix argument, previous highlights
+ are kept, so several calls to this command can be stacked.
- {{{kbd(M-g n)}}} or {{{kbd(M-g M-n)}}} (~next-error~) ::
@@ -3663,10 +3663,10 @@ ** Search Options in File Links
- =/REGEXP/= ::
- Do a regular expression search for {{{var(REGEXP)}}}. This uses the
- Emacs command ~occur~ to list all matches in a separate window. If
- the target file is in Org mode, ~org-occur~ is used to create
- a sparse tree with the matches.
+ Do a regular expression search for {{{var(REGEXP)}}} (see [[*Regular
+ Expressions]]). This uses the Emacs command ~occur~ to list all
+ matches in a separate window. If the target file is in Org mode,
+ ~org-occur~ is used to create a sparse tree with the matches.
As a degenerate case, a file link with an empty file name can be used
to search the current file. For example, =[[file:::find me]]= does
@@ -4978,8 +4978,9 @@ ** Tag Hierarchy
Furthermore, the members of a group tag can also be regular
expressions, creating the possibility of a more dynamic and rule-based
-tag structure. The regular expressions in the group must be specified
-within curly brackets. Here is an expanded example:
+tag structure (see [[*Regular Expressions]]). The regular expressions in
+the group must be specified within curly brackets. Here is an
+expanded example:
#+begin_example
,#+TAGS: [ Vision : {V@.+} ]
@@ -5321,7 +5322,7 @@ ** Property Searches
tree is created with all entries that define this property with the
given value. If you enclose the value in curly braces, it is
interpreted as a regular expression and matched against the property
- values.
+ values (see [[*Regular Expressions]]).
** Property Inheritance
:PROPERTIES:
@@ -8913,8 +8914,9 @@ *** Matching tags and properties
#+cindex: regular expressions, with tags search
Instead of a tag, you may also specify a regular expression enclosed
-in curly braces. For example, =work+{^boss.*}= matches headlines that
-contain the tag =:work:= and any tag /starting/ with =boss=.
+in curly braces (see [[*Regular Expressions]]). For example,
+=work+{^boss.*}= matches headlines that contain the tag =:work:= and
+any tag /starting/ with =boss=.
#+cindex: group tags, as regular expressions
Group tags (see [[*Tag Hierarchy]]) are expanded as regular expressions.
@@ -8954,7 +8956,7 @@ *** Matching tags and properties
#+begin_example
+work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2
- +With={Sarah|Denny}+SCHEDULED>="<2008-10-11>"
+ +With={Sarah\|Denny}+SCHEDULED>="<2008-10-11>"
#+end_example
#+texinfo: @noindent
@@ -8984,7 +8986,7 @@ *** Matching tags and properties
not =boss=, which also have a priority value =A=, a =Coffee= property
with the value =unli
Re: [BUG] Creating sparse tree with regexp property matches
Timothy [2021-09-01 Wed 18:28] wrote: > Hi Daniel, > > Thanks Daniel, I’ve just had a quick read and it looks good to me. If anyone > else has comments this would be a great time to jump in :) > > I haven’t seen `' links before, it seems like there’s one > other in the manual. Do you know if they work well with the exported forms of > the manual? > There's actually another link with a bit different format: Testing it: in the PDF it doesn't do anything but in the compiled HTML file it leads to the right section. In Emacs obviously it will jump correctly to the info node. I did "discover" Emacs regular expression node which I think is friendlier than Elisp's (and contains it) so I'll replace the link; see Daniel Fleischer
Re: [BUG] Creating sparse tree with regexp property matches
Hi Timothy,
Attached is my patch.
Best,
*Daniel Fleischer*
>From 05602a3eb453672893e7e92cc0384e1b6b7784aa Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Tue, 31 Aug 2021 20:01:47 +0300
Subject: [PATCH] org-manual: added section about regular expressions
Telling users it's based on Elisp regular expressions, linking to its
info node and putting some links to this new node in places where regexp
are presented.
Signed-off-by: Daniel Fleischer
---
doc/org-manual.org | 78 --
1 file changed, 47 insertions(+), 31 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 10e0baa28..38884ad72 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -916,16 +916,16 @@ ** Sparse Trees
#+kindex: C-c / /
#+findex: org-occur
#+vindex: org-remove-highlights-with-change
- Prompts for a regexp and shows a sparse tree with all matches. If
- the match is in a headline, the headline is made visible. If the
- match is in the body of an entry, headline and body are made
- visible. In order to provide minimal context, also the full
- hierarchy of headlines above the match is shown, as well as the
- headline following the match. Each match is also highlighted; the
- highlights disappear when the buffer is changed by an editing
- command, or by pressing {{{kbd(C-c C-c)}}}[fn:8]. When called with
- a {{{kbd(C-u)}}} prefix argument, previous highlights are kept, so
- several calls to this command can be stacked.
+ Prompts for a regexp (see [[*Regular Expressions]]) and shows a sparse
+ tree with all matches. If the match is in a headline, the headline
+ is made visible. If the match is in the body of an entry, headline
+ and body are made visible. In order to provide minimal context,
+ also the full hierarchy of headlines above the match is shown, as
+ well as the headline following the match. Each match is also
+ highlighted; the highlights disappear when the buffer is changed by
+ an editing command, or by pressing {{{kbd(C-c C-c)}}}[fn:8]. When
+ called with a {{{kbd(C-u)}}} prefix argument, previous highlights
+ are kept, so several calls to this command can be stacked.
- {{{kbd(M-g n)}}} or {{{kbd(M-g M-n)}}} (~next-error~) ::
@@ -3663,10 +3663,10 @@ ** Search Options in File Links
- =/REGEXP/= ::
- Do a regular expression search for {{{var(REGEXP)}}}. This uses the
- Emacs command ~occur~ to list all matches in a separate window. If
- the target file is in Org mode, ~org-occur~ is used to create
- a sparse tree with the matches.
+ Do a regular expression search for {{{var(REGEXP)}}} (see [[*Regular
+ Expressions]]). This uses the Emacs command ~occur~ to list all
+ matches in a separate window. If the target file is in Org mode,
+ ~org-occur~ is used to create a sparse tree with the matches.
As a degenerate case, a file link with an empty file name can be used
to search the current file. For example, =[[file:::find me]]= does
@@ -4978,8 +4978,9 @@ ** Tag Hierarchy
Furthermore, the members of a group tag can also be regular
expressions, creating the possibility of a more dynamic and rule-based
-tag structure. The regular expressions in the group must be specified
-within curly brackets. Here is an expanded example:
+tag structure (see [[*Regular Expressions]]). The regular expressions in
+the group must be specified within curly brackets. Here is an
+expanded example:
#+begin_example
,#+TAGS: [ Vision : {V@.+} ]
@@ -5321,7 +5322,7 @@ ** Property Searches
tree is created with all entries that define this property with the
given value. If you enclose the value in curly braces, it is
interpreted as a regular expression and matched against the property
- values.
+ values (see [[*Regular Expressions]]).
** Property Inheritance
:PROPERTIES:
@@ -8913,8 +8914,9 @@ *** Matching tags and properties
#+cindex: regular expressions, with tags search
Instead of a tag, you may also specify a regular expression enclosed
-in curly braces. For example, =work+{^boss.*}= matches headlines that
-contain the tag =:work:= and any tag /starting/ with =boss=.
+in curly braces (see [[*Regular Expressions]]). For example,
+=work+{^boss.*}= matches headlines that contain the tag =:work:= and
+any tag /starting/ with =boss=.
#+cindex: group tags, as regular expressions
Group tags (see [[*Tag Hierarchy]]) are expanded as regular expressions.
@@ -8954,7 +8956,7 @@ *** Matching tags and properties
#+begin_example
+work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2
- +With={Sarah|Denny}+SCHEDULED>="<2008-10-11>"
+ +With={Sarah\|Denny}+SCHEDULED>="<2008-10-11>"
#+end_example
#+texinfo: @noindent
@@ -8984,7 +8986,7 @@ *** Matching tags and properties
not =boss=, which also have a priority value =A=, a =Coffee= property
with the value =unlimited=, an =EFFORT= property that is numerically
Re: Bug: Error making documentation 9.4.6
Hi Marco, Sorry about that, I'm new in contributing to org. I found the solution in the mailing list[1]. There was an old version of `makeinfo'. Daniel Fleischer Footnotes _ [1] <https://orgmode.org/list/CAGY83EfXn8jBUu1jDqCnuXMyxYc1efcf8OEP2su2=vhm9d6...@mail.gmail.com/>
Bug: Error making documentation 9.4.6
Hi,
Pulling master @ 1690fbd88, calling `make doc' leads to error:
org-version: 9.4.6 (release_9.4.6-635-g1690fb)
makeinfo --no-split org.texi -o org.info
org.texi:6: warning: unrecognized encoding name `UTF-8'.
org.texi:810: Unknown command `arrow'.
org.texi:810: Misplaced {.
org.texi:810: Misplaced }.
org.texi:810: Unknown command `arrow'.
org.texi:810: Misplaced {.
org.texi:810: Misplaced }.
org.texi:821: Unknown command `arrow'.
org.texi:821: Misplaced {.
org.texi:821: Misplaced }.
org.texi:2627: Unknown command `arrow'.
org.texi:2627: Misplaced {.
org.texi:2627: Misplaced }.
org.texi:2629: Unknown command `arrow'.
org.texi:2629: Misplaced {.
org.texi:2629: Misplaced }.
org.texi:3548: Unknown command `arrow'.
org.texi:3548: Misplaced {.
org.texi:3548: Misplaced }.
org.texi:3548: Unknown command `arrow'.
org.texi:3548: Misplaced {.
org.texi:3548: Misplaced }.
makeinfo: Removing output file `org.info' due to errors; use --force to preserve.
make[1]: *** [org] Error 1
make: *** [info] Error 2
–
Daniel Fleischer
Re: [BUG] Creating sparse tree with regexp property matches
Timothy [2021-08-31 Tue 19:27] wrote: > Hi Cassio, > >> Ah! Can’t believe I didn’t try that. Well, at least the docs can >> benefit from my confusion. > > Would you be interested in making a patch for the docs, or would you rather > leave that to someone else? Actually I want to do that. I had an idea to add a node (in org) "reminding" people that all mentions of regex refer to elisp regex, which could be different than what people usually know (PCRE) and point them toward the elisp regex node. I think this point can confuse non technical people when they are starting to use orgmode and there should be a mention in the org manual. Most notably are the alternation \| instead of | and \(...\) grouping instead of (...). Best, *Daniel Fleischer*
Re: [BUG] Creating sparse tree with regexp property matches
On Wed, Aug 25 2021, Cassio Koshikumo wrote:
> Hello all,
>
> I think there's a bug with `org-make-tags-matcher' when creating a sparse tree
> using property matching with regular expressions and "or" terms. Take the
> example given in the manual:
>
> +work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2
>+With={Sarah|Denny}+SCHEDULED>="<2008-10-11 Sat>"
>
> If we isolate just this part:
>
> +With={Sarah|Denny}
>
> The resulting sparse tree does not match the right
> headings. The function generates the following `tagsmatcher':
>
> (progn
> (setq org-cached-props nil)
> (or
>(and
> (member
> #("Denny" 0 5
>(regexp t))
> tags-list))
>(and
> (member "With" tags-list
>
> There're checks for "Denny" (as a regexp) and "With" (as a string) --- this is
> supposed to be the property name, not a search term. They are both checked for
> in `tags-list'. And, finally, "Sarah" is nowhere to be seen.
>
> The problem, as far as I can tell, is that splitting the input at `|' to get
> the
> `orterms' does not work with the regular expression the function uses to find
> the constituent parts of each term. In this example, splitting the input at
> `|'
> makes one side get the opening brace and the other the closing brace, while
> the
> regexp expects both being present. Since the regexp doesn't fully match, the
> terms are all parsed wrong. (The function doesn't recognize "With" as property
> name, for instance.) I'm still messing with it but, for now, don't really know
> how to fix the problem. I don't 100% understand the function yet...
>
> Regards,
Hi, the solution is that it's elisp based regex, so OR is indicated with
\| instead of just |. It might be good idea to correct the example.
Best,
*Daniel Fleischer*
Bug: Org Clock continues in canceled captured note [9.4 (9.4-53-gc97446-elpaplus @ /Users/df/.emacs.d/elpa/org-plus-contrib-20201130/)]
When using org-capture with :clock-in or when starting the clock manually when writing the note, then after canceling the note using C-c C-k, the clock continues as can be seen in the modeline. Reproduced also in a clean 'emacs -Q' setup. Emacs : GNU Emacs 28.0.50 (build 1, x86_64-apple-darwin19.6.0, NS appkit-1894.60 Version 10.15.7 (Build 19H15)) of 2020-12-01 Package: Org mode version 9.4 (9.4-53-gc97446-elpaplus @ /Users/df/.emacs.d/elpa/org-plus-contrib-20201130/) Daniel Fleischer
org-num-mode for RTL languages
Hi, Org-num-mode doesn't work for RTL language (e.g. Hebrew) when `bidi-paragraph-direction` is set to `left-to-right`. It does work when one sets `bidi-paragraph-direction` to nil. Example text: * Test * עברית * עוד אחד * Back to English I would expect it to work either way because sometimes the file reads better when everything is aligned left-to-right. Thanks, Daniel
