Good news! This is the last of my "things I want to contact the mailing list
about" backlog
So, I recently wanted to be able to create a radar chart in org, using #+PLOT
without a 500 character #+PLOT line.
I started with advice-override, but quickly realised it would be better just to
Another email, another request
Hoping that you aren't tired of me yet, I have … (drum-roll) another feature
request!
This time, I'm wanting to be able to use the lovely org latex preview
functionality for more than just the default blocks.
For instance, I'm interested in applying it to mhchem
It's me again!
We're now onto email 2/4. This one is a wish-list of entry points for
customising export functionality (well, styling).
I'm a big fan of trying to make my documents look snazzy with minimal work
(i.e. by cramming all the snazzyness in the back-end), which is why I was
thrilled
Hello All!
I love the first-class LaTeX support in Org-mode, and discovering that
org-edit-special worked inside LaTeX environments was a joyous moment for me.
Shortly after that though, I was disappoint to discover that this didn't work
with inline LaTeX equations \( … \) or LaTeX display
George Sokolsky writes:
> I had to apply it manually on the latest org-20200518 (line numbers
> changed in this new version or me too lame) - the patch seem to fix the
> below problem and works just fine!
The patch was against the master branch (specifically 9bc0cc7fb), not
the mai
ISSUE: An author should expect a compiler to avoid claiming authorship
over target code, however, currently the org-mode publish document
processor silently inserts licensed content into target documents by
default.
SOLUTION: The following script is a drop-in-replacement which provides
the
Kaushal Modi writes:
> At some point in the past month or so, I have noticed that on Org master,
> #+author: does not set the author to empty in the exports.
>
> Simply example to reproduce:
Thanks for the minimal example.
> I looked through the commits on master in the past month, but I don't
Doesn’t Gogs have a nice issue tracker functionality?
--
James Miller
james.ryland.mil...@gmail.com
Anthony Carrico writes:
> Does org-mode have an issue tracker, to keep track of which issues are
> active, or is it just this mailing list?
Just this mailing list.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors."
Does org-mode have an issue tracker, to keep track of which issues are active,
or is it just this mailing list?
--
Anthony Carrico
This just might be the functionality that makes me learn elisp. :)
--
James Miller
james.ryland.mil...@gmail.com
You need to quote the asterisk with a comma:
#+begin_example
,* I am not supposed to be a section
#+end_example
See
(info "(Org) Literal Examples")
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
John Hendy writes:
> I ran into this as well and did not see a response back from the list
> yet. Emailed about just this issue last week.
>
> https://www.mail-archive.com/emacs-orgmode@gnu.org/msg127933.html
>
> John
>
>
> On Sat, May 16, 2020 at 10:21 AM Max Mustermann
> wrote:
>>
>> Hey,
>>
> As you noticed, using Org Element is a no-go, unfortunately. Parsing an
> element is a O(N) operation by the number of elements before it in
> a section. In particular, it is not bounded, and not mitigated by
> a cache. For large documents, it is going to be unbearably slow, too.
Ouch. I
I ran into this as well and did not see a response back from the list
yet. Emailed about just this issue last week.
https://www.mail-archive.com/emacs-orgmode@gnu.org/msg127933.html
John
On Sat, May 16, 2020 at 10:21 AM Max Mustermann
wrote:
>
> Hey,
> On
"James R Miller" writes:
> It just seems like a regression to me instead of a fix. Functionality
> was removed instead of fixed.
I am not sure about how helpful your message is.
I am not opposed to the fancy indentation you want: if you want to fix
it properly, you can give it a go. The code
Hello,
"Dauer, Michael" writes:
> According to my tests this is not fixed. Same use case as originally
> reported still fails: Undefined Org macro: author; aborting
>
> I also use #OPTIONS: author:nil, which is necessary to prevent that the
> export is concluded by an author line.
>
> Would you
Hello,
"Dauer, Michael" writes:
> Why would the following break the export?
I never said the following would break export. I said your initial
proposal would, i.e. using ".". You changed it meanwhile.
> #+BEGIN: columnview :indent t :id local
> | ITEM| a |
> |-+---|
> |
Why would the following break the export?
#+BEGIN: columnview :indent t :id local
| ITEM| a |
|-+---|
| column view | 7 |
| ··item1 | 3 |
| item1.1 | 3 |
| ··item2 | 4 |
#+END
U+2063 would be invisible. And the ASCII export could just substitute it
with Blank.
Am
According to my tests this is not fixed. Same use case as originally
reported still fails: Undefined Org macro: author; aborting
I also use #OPTIONS: author:nil, which is necessary to prevent that the
export is concluded by an author line.
Would you please verify the fix. Maybe I did something
Hello,
Ihor Radchenko writes:
> Apparently my previous email was again refused by your mail server (I
> tried to add patch as attachment this time).
Ah. This is annoying, for you and for me.
> The patch is in
> https://gist.github.com/yantar92/6447754415457927293acda43a7fcaef
Thank you.
>>
Am 18.05.20 um 15:57 schrieb Kaushal Modi:
> I looked through the commits on master in the past month, but I don't
> see any author-specific change that would affect *all* the exporter
> backends.
>
> Can anyone else reproduce this issue?
Same observation here (org master from about a week ago,
It just seems like a regression to me instead of a fix. Functionality was
removed instead of fixed.
--
James Miller
james.ryland.mil...@gmail.com
Hello,
At some point in the past month or so, I have noticed that on Org master,
#+author: does not set the author to empty in the exports.
Simply example to reproduce:
=
#+author:
Test
=
Run C-c C-e t A
Expected output:
=
Table of Contents
_
Test
=
Hello,
"Gerry Agbobada" writes:
> I found on Worg a "draft" for org syntax description :
> https://orgmode.org/worg/dev/org-syntax.html
>
> Do you think this paper marked as draft is good enough to use as
> a source to make a parser ?
It is "good enough", but possibly slightly inaccurate at
Hello,
silipwn writes:
> On removing the variable, it works fine. The GPG configuration directly
> takes my mail address to get the key. The other issue was I also had
> a revoked key with the same email, that
> might have been causing an error, mentioned in the earlier mail.
While trying to
Kyle, could you please apply the patch to the org repository?
Thank you
George
Bastien writes:
> Hi George,
>
> George Sokolsky writes:
>
>> For avoidance of doubt - this is Kyle's patch, not mine (thank you
>> Kyle!)
>
> Sorry for the confusion, I thought you were asking for permission to
Hi George,
George Sokolsky writes:
> For avoidance of doubt - this is Kyle's patch, not mine (thank you
> Kyle!)
Sorry for the confusion, I thought you were asking for permission to
commit the patch directly yourself. Kyle can of course apply it when
he wants.
> Bastien, do you mean that
Dear members of the org-mode mailing list,
a week ago I spent some time to set up a capture template to
directly write appointments to my calendar file (i.e. to write
diary entries). It looks as follows:
("d" "Diary entry" entry (file+datetree+prompt
"~/MPIK-Nextcloud/emacs/.org/kalender.org")
For avoidance of doubt - this is Kyle's patch, not mine (thank you Kyle!)
Bastien, do you mean that this patch will be in the next weekly org build on
melpa?
Thank you
George
Bastien writes:
> Hi George,
>
> thanks for your patch!
>
> George Sokolsky writes:
>
>> I'm trying to add Bastien
Hi George,
thanks for your patch!
George Sokolsky writes:
> I'm trying to add Bastien into recepients of this e-mail - or could
> anyone please help with commiting the below code into the org
> repository?
Anyone with write access to the repository can apply it.
If you plan to make regular
Thank you very much Kyle for the patch you provided!
I had to apply it manually on the latest org-20200518 (line numbers
changed in this new version or me too lame) - the patch seem to fix the
below problem and works just fine!
IMHO using "#+FILETAGS: ARCHIVE" is one of legit
Garjola Dindi writes:
> On Tue 12-May-2020 at 12:59:22 +02, "Loris Bennett"
> wrote:
>> Eric S Fraga writes:
>>
>>> On Tuesday, 12 May 2020 at 09:29, Loris Bennett wrote:
The Nextcloud instance at work is version 15 and is accessible via the
browser, but there was some outage
Hello,
"James R Miller" writes:
> Was there really not a way to keep fancy description list indentation
> instead of removing it entirely?
I don't know if there is a way, but the implementation did not work with
nested lists.
> I have almost a decade of org files
> that use description lists,
> James R Miller writes:
> Hi all, Was there really not a way to keep fancy description list
> indentation instead of removing it entirely? I have almost a
> decade of org files that use description lists, and it really
> helps have the description items called out from the
35 matches
Mail list logo
