Hello Ihor.
Ihor Radchenko writes:
> Max Nikulin writes:
>
>>> Is major-mode for editing asymptote code available easily?
>>> I was unable to find anything relevant in ELPA and non-GNU ELPA.
>>
>> I am not an asymptote user, but the following suggests that it may be
>> installed with asymptot
Greetings Munyoki.
Munyoki Kilyungi writes:
> Hi Jarmo!
>
> Jarmo Hurri anaandika:
>
>> I hereby volunteer to maintain ob-asymptote.el.
>
> Nice!
>
>> This file has been moved
>> to org-contrib, but I would like it to be brought back into Org itself.
>>
>> I strongly feel that Asymptote is wa
Greetings.
I see that ob-processing.el has currently no maintainer. I volunteer.
All the best,
Jarmo
On 21/07/2022 22:39, Juan Manuel Macías wrote:
Max Nikulin writes:
I would vote for a custom variable, at the global level (I agree with
the options you suggest) and at the document level, to economize,
perhaps this would be enough to avoid the code of both babel and
polyglossia:
#+latex_header
Max Nikulin writes:
> Form my point of view it is unnecessary magic. Originally #+latex_header
> is intended for valid LaTeX code
OK, so why not just:
#+latex_header: % NOLANG
?
I think this has in its favor: a) it is simple and obvious to remember;
b) it's a single string, and of course c) i
Ihor Radchenko writes:
> The fix is attached.
Applied onto main via b6098500a.
Best,
Ihor
Ihor Radchenko writes:
> I propose a new make target: make repro
> It will run the commands we already suggest, but without a need to
> create minimal file, pass all that arguments to emacs, etc
Applied onto main via b713b9afa.
Best,
Ihor
Juan Manuel Macías writes:
> OK, so why not just:
>
> #+latex_header: % NOLANG
>
> ?
Forget this. On second thought, I think that the option you proposed
"#+LaTeX_Header: % \usepackage{babel}" is much better.
(I don't know where my head was and I didn't remember there was a
string-match, so your
Ihor,
> Dear All, may we should provide a normal header arg as an equivalent of
> switches? Honestly, this whole switch syntax sounds unnecessary and only
> over-complicates things.
i'm a fan.
>>> "AB" == Arne Babenhauserheide writes:
> Uwe Brauer writes:
>> So the question is, how to generate this file. Maybe there is a
>> ChangeLog--> ChangeLog.org exporter/converter?
>>
>> https://github.com/johnlepikhin/el-conventional-changelog/blob/master/conventional-changelog.el
> I see onl
Eric,
> Have a look at #+SETUP but also consider the autoinsert package.
sorry, but what is the autoinsert package?
cheers, Greg
>>> "UB" == Uwe Brauer writes:
>>> "UB" == Uwe Brauer writes:
>> Hi
>> I attach a file that hopefully explains the problem.
>> That file contains 109 heading, each heading has 17 different
>> properties when all of them are included in the
> It seems that
> #+begin_src emacs-lisp :results si
hi. does anyone have any code, or know of any existing package, that
would allow for some sort of form-like (or "transient"-like) interface
for adding rows to an org-mode table? in particular, that provides some
sort of =completing-read= interface for a given set of choices for a
given column, et
On Friday, 22 Jul 2022 at 06:27, alain.coch...@unistra.fr wrote:
> Plus one must revisit the file when changing the value of
> that variable.
You can reload local variables by hitting C-c C-c on the #+title: line,
for instance.
--
: Eric S Fraga, with org release_9.5.4-557-g3bbbf7 in Emacs 29.
On Friday, 22 Jul 2022 at 19:05, Greg Minshall wrote:
> sorry, but what is the autoinsert package?
It comes with Emacs:
,[ C-h f auto-insert RET ]
| auto-insert is an autoloaded interactive compiled Lisp function in
| ‘autoinsert.el’.
|
| (auto-insert)
|
| Insert default contents into new f
Fraga, Eric wrote:
> It comes with Emacs:
ah! thanks!
cheers, Greg
Dear Benoit,
this does sound like what I have done for my blog: I write all blog
posts as org files in a single directory called "posts" and publish them
through org-publish. In each file, I define tags via the =FILETAGS=
keyword.
Upon publishing, I set =:sitemap-format-entry= in
=org-publish-p
Fraga, Eric writes on Fri 22 Jul 2022 17:09:
> On Friday, 22 Jul 2022 at 06:27, alain.coch...@unistra.fr wrote:
> > Plus one must revisit the file when changing the value of
> > that variable.
>
> You can reload local variables by hitting C-c C-c on the #+title: line,
> for instance.
Ah O
Hello,
There seems to be an issue with using ":comments link" when the source block is
at the root of the org file instead of under a heading. This happens using emacs -Q.
A file containing something like this:
#+begin_src elisp :tangle yes :comments link
(message "test")
#+end_src
tangles to
Hello,
I'm using emacs from commit f258f67 (quite recent) and org from commit
39005dc (quite recent).
I'm using native compilation and PGTK.
I was able to reproduce this with 'emacs -Q'
When trying to update a clocktable I get the following backtrace (with a
little bit removed).
Debugger enter
Morgan Smith writes:
> I'm using emacs from commit f258f67 (quite recent) and org from commit
> 39005dc (quite recent).
>
> I'm using native compilation and PGTK.
> Debugger entered--Lisp error: (invalid-function org-encode-time)
> org-encode-time((0 0 0 21 7 2022 4 t -14400))
> org-matcher-
Elias Kueny writes:
> There seems to be an issue with using ":comments link" when the source block
> is at the root of the org file instead of under a heading. This happens using
> emacs -Q.
>
> A file containing something like this:
> #+begin_src elisp :tangle yes :comments link
> (message "
András Simonyi writes:
> ...of course, I managed to leave a typo in the manual patch, please
> ignore the earlier version and consider the attached one.
Thanks!
Could you please create a dedicated subsection under "15 Citation
handling" instead of documenting PRINT_BIBLIOGRAPHY together with exp
Sébastien Miquel writes:
> The uses are maybe too niche to warrant the breaking change. A syntax
> extension like
> : var=block-id[]
> seems possible, even though brackets are already overloaded.
This sounds better. Using brackets will actually make a lot of sense.
Currently, we have roughly
Juan Manuel Macías writes:
> Here is a new version of the patch, with the fixes added.
Thanks! Considering that the followup discussion deviated from the
substance of the patch towards related design issues, I have decided to
marge the patch as is. We can decide on handling AUTO staff later - it
Janek F writes:
> When setting org-id-method to 'ts or 'org,
> org-attach seems to use org-attach-id-ts-folder-format
> to create its hierarchy.
>
> However I tend to customize IDs for important files by hand,
> causing any attempt to use org-attach on that file to fail
> if the ID is shorter tha
Janek F writes:
> With the following configuration (on top of vanilla Doom, but that doesn't
> seem to be related), when trying to export to Markdown an org-mode file with
> broken links, the export omits all content under headlines:
>
> (setq org-export-with-toc nil
> org-export-with-bro
27 matches
Mail list logo
