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
>
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
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
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
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
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
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
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
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
>>> "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
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.
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
12 matches
Mail list logo
