Re: Agenda buffer name after following a time stamp
Garjola Dindi writes: [...] > Steps to reproduce: > > 1. Press on [2020-10-22 Thu]. This generates the agenda for >that date in a buffer named "*Org Agenda(a:2020-10-22)" > 2. Close the agenda with "q" or "x" > 3. invoke the org-agenda dispatcher, choose t (or any other view except >"a"). This generates a buffer named "*Org Agenda(a:2020-10-22)" >instead of "*Org Agenda*". > > Using the interactive commands org-todo-list has the same behaviour. > > However, using "a" in the agenda dispatcher or calling org-agenda-list > generates a buffer correctly called "*Org Agenda*". > > I have tried with "emacs -q" and the behaviour is the same. > > Is this an expected behaviour? I have not been able to find the > information in the manual. Thanks for the report, and the steps to trigger the issue. Should be fixed by 95af0a244.
Re: [PATCH] Async session eval (2nd attempt)
Jack Kamm writes: > This patch adds asynchronous evaluation for session blocks in > Python. It also adds functionality to implement async session eval for > other languages using ob-comint.el. > > To test the attached patch, add ":async" to a Python session block > with a long computation (or "time.sleep") in it. Upon evaluation, your > Emacs won't freeze to wait for the result -- instead, a placeholder > will be inserted, and replaced with the true result when it's ready. > > [...] Thanks. Sounds exciting :) So... have any Babel users on the list given this a spin? Any comments or feedback?
Re: [PATCH] org-manual.org: Remove languages list and update worg link
ian martins writes: > I pushed two days ago, but the manual hasn't updated yet. I guess it > doesn't update on git hooks like worg. is there a scheduled process or is > there something that must be done? The online manual corresponds to the latest release and updated with each release (as far as I know, though hopefully Bastien or others will correct me if I'm wrong).
Re: [PATCH] add new link type "contact:" for org-contacts.el
After waited some days, still no reponse, so I popup this email. Can some Org maintainer review my patch? Thanks. It does not changed org-contacts.el core logic. Just added a new link type. Should be easy to review. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Fri, Oct 30, 2020 at 3:44 PM stardiviner wrote: > Accidentally pressed send button without email body. > Hope org-contacts.el author can review this patch. > > [stardiviner] GPG key ID: 47C32433 > IRC(freeenode): stardiviner Twitter: @numbchild > Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 > Blog: http://stardiviner.github.io/ > > > On Fri, Oct 30, 2020 at 3:35 PM stardiviner wrote: > >> >> >> [stardiviner] GPG key ID: 47C32433 >> IRC(freeenode): stardiviner Twitter: @numbchild >> Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 >> Blog: http://stardiviner.github.io/ >> >
Is there possibility to provide back links to each finely grained part of Org file?
In reference to Doug Engelbart's vision: https://www.dougengelbart.org/content/view/116/#7j I am asking if there is feature in Org mode that could generate a back link or #name or other tags in export so that each part of Org file can be later finely referenced? Example may be seen on the above link. On the right side there are 7j or 7d names to which anybody can link to pin point specific paragraph. I know that #names exist in HTML export for *** headings. Do they or can they exist for every paragraph or item listed? Jean
bug#44524: 28.0.50; Wrong place saved in org file with save-place-mode
Package: emacs,org-mode 0. emacs -Q 1. enable save-place-mode 2. visit an org file with a single line: #+DATE: 2020-11-08 The cursor always jumps to the fixed place inside the date, and doesn't remember its previous position. Here is a fix to not set buffer-file-name (that causes save-place-mode to save wrong place for that file name) in a temporary buffer: diff --git a/lisp/org/org-element.el b/lisp/org/org-element.el index be74dfdbef..d1fa777aa6 100644 --- a/lisp/org/org-element.el +++ b/lisp/org/org-element.el @@ -4144,7 +4144,8 @@ org-element-parse-secondary-string (dolist (v local-variables) (ignore-errors (if (symbolp v) (makunbound v) - (set (make-local-variable (car v)) (cdr v) + (unless (memq (car v) '(buffer-file-name buffer-file-truename)) + (set (make-local-variable (car v)) (cdr v)) ;; Transferring local variables may put the temporary buffer ;; into a read-only state. Make sure we can insert STRING. (let ((inhibit-read-only t)) (insert string))
manual omission - effort command in agenda remote editing section
The following command is missing from section 11.5, Commands in the Agenda Buffer, Remote editing commands C-c C-x e or short e (org-set-effort) -- = Ian Garmaise Consultant Phorix Solutions Group ia...@phorixsol.com Toronto cell: 416.432.2251 NYC: 917.512.9535 https://www.linkedin.com/in/igarmaise/ http://www.PhorixSol.com
export of coderefs to reveal.js
Hi! Using coderefs for normal html export works fine. On mouseover the target line is highlighted. But exporting the same org file to reveal.js with org-reveal I get the following error message (in Chrome): VM22943 slide-org57a7ad2:249 Uncaught ReferenceError: CodeHighlightOn is not defined at HTMLAnchorElement.onmouseover (VM22943 slide-org57a7ad2:249) There is no CodeHighlightOn/Off script in the exported file. Is it possible to get this working? Johannes
Re: [PATCH] org-manual.org: Remove languages list and update worg link
I pushed two days ago, but the manual hasn't updated yet. I guess it doesn't update on git hooks like worg. is there a scheduled process or is there something that must be done? On Thu, Nov 5, 2020 at 11:03 PM Kyle Meyer wrote: > ian martins writes: > > > Subject: [PATCH] org-manual.org: Remove language list and fix Worg link > > > > * doc/org-manual.org: Remove the language list and fix the Worg link > > since the languages page has moved. Renumber footnotes. > > > > The language list in the manual is missing many languages. Rather > > than trying to keep the list up to date in two places that link to > > each other, this removes the list from the manual which is updated > > less frequently. There were a few footnotes in the table, so this > > also renumbers the remaining footnotes. > > Sounds like a good idea to me. > > > The languages page was moved in Worg to make it the index page in the > > languages directory. This updates the link in the manual to point to > > its new location. > > --- > > doc/org-manual.org | 103 + > > 1 file changed, 38 insertions(+), 65 deletions(-) > [...] > > -[fn:160] Note that, for ~org-odd-levels-only~, a level number > > +[fn:158] Note that, for ~org-odd-levels-only~, a level number > > corresponds to order in the hierarchy, not to the number of stars. > > > > [fn:161] If you move entries or Org files from one directory to > > Hmm, the 158 to 161 jump after your renumbering caught my eye, but it > looks like it's orthogonal to your changes. There was a bad merge > conflict resolution in 9410fbe06 that unlinked this definition from its > reference (one of the two [fn:89]s). I'll clean it up after your > changes land. >
Re: export +A+ to latex, xout and not sout
>>> "T" == TEC writes:
Hi Timothy
> Hi Uwe,
> Uwe Brauer writes:
>> I'd rather prefer to have \xout{A} instead of \sout{A}
>> How can I achieve that?
> How about this:
> (setcdr (assoc 'strike-through org-latex-text-markup-alist)
>"\\xout{%s}")
A pure lisp solution, I see, I thought one could add something in the
export options, but never mind.
> Hope that helps,
It does so very much, thanks.
smime.p7s
Description: S/MIME cryptographic signature
Re: export +A+ to latex, xout and not sout
Hi Uwe,
Uwe Brauer writes:
I'd rather prefer to have \xout{A} instead of \sout{A}
How can I achieve that?
How about this:
(setcdr (assoc 'strike-through org-latex-text-markup-alist)
"\\xout{%s}")
Hope that helps,
Timothy.
export +A+ to latex, xout and not sout
Hi
When I export an org file that contains constructs such as +A+ to a
Latex files, it gets converted to \sout{A}.
I'd rather prefer to have \xout{A} instead of \sout{A}
How can I achieve that?
Thanks and regards
Uwe Brauer
