Ihor Radchenko writes:
> I tried to make sure that org-map-continue-from is not broken, but your
> scenario is apparently not covered by our tests.
>
> Let me investigate and fix this.
It turned out to be more tricky than I thought.
Fixed by 06f58e475
Let me know if you are still seeing the pr
Hi Christopher,
> This might need to mentioned in Org manual and in ob-python.el source
> code with comment. WDYT?
The main documentation for this is in the Worg page for ob-python, in
particular see the section "Return values":
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.
Uwe Brauer writes:
> [[S/MIME Signed Part:Undecided]]
"TC" == Tim Cross writes:
>
>> Uwe Brauer writes:
>
>
>> For problem 1, I suspect you will need to either change the date format
>> or tell org what the date format is. It won't work trying to sort
>> numerically as those values are n
Aloha Matt,
Matt writes:
> Wow. Nice work!
Thanks. I pushed things to Worg, if you haven't seen already
(https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html).
If you read it and find anything missing or unclear, please let
me know. I'm still waiting on work to sign the
> Wow. Nice work!
Thanks. I pushed things to Worg, if you haven't seen already
(https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html). If
you read it and find anything missing or unclear, please let me know. I'm still
waiting on work to sign the FSF disclaimer in order to
Max,
> On Dec 31, 2021, at 4:05 AM, Max Nikulin wrote:
>
>
> Should some function a macro be provided to facilitate declaring languages as
> data format (config files, JSON, YAML, etc.) rather than executable source
> code?
I think we already have this in the form of export blocks, viz.
#+n
Aloha Matt,
Wow. Nice work!
All the best,
Tom
Matt writes:
> Contributions to Worg aren't similarly restricted. Feel free
> to
> push material there in the meantime.
Looks like the email finally got sent to the right person at my
company. Who knows how long it will take for them to
On Friday, 31 Dec 2021 at 17:05, Uwe Brauer wrote:
> Thanks the \{4\} surprise me. I tried
>
> (query-replace-regexp "\\(\\<[0-9]*\\)\\([\\.]\\)\\([0-9]*\\>\\)" "\\3\\2\\1")
Not sure what this is trying to do. If it's going from <2021-12-31> to
31.12.2021, you shouldn't escape the < or >, you ar
>>> "ESF" == Eric S Fraga writes:
> On Friday, 31 Dec 2021 at 14:21, Uwe Brauer wrote:
>> ⚠️ Caution: External sender
>>
>>
>> Hi
>>
>> Does anybody know about a function that would convert between
>> date format like 31.12.2021 to <2020-12-31> and back?
> This is Emacs, of course, so you c
Juan Manuel Macías writes:
>> The priority appears to be intentional.
>
> I see. But then the compatibility with the rest of the emphasis is
> broken. I mean, the user would expect things like (_underline_) will be
> exported as (\uline{underline}), in the same way that (/emphasis/) is
> exported
On Friday, 31 Dec 2021 at 14:21, Uwe Brauer wrote:
> ⚠️ Caution: External sender
>
>
> Hi
>
> Does anybody know about a function that would convert between
> date format like 31.12.2021 to <2020-12-31> and back?
This is Emacs, of course, so you could use query-replace-regexp (M-%)
with, for inst
Hi
Does anybody know about a function that would convert between
date format like 31.12.2021 to <2020-12-31> and back?
Thanks
Uwe Brauer
On 30/12/2021 15:00, Rudolf Adamkovič wrote:
#+property: header-args:bibtex+ :eval yes
Why do you set ":eval yes" explicitly for bibtex if you believe that it
should not be executed?
I suppose, the following may be considered as a complete example
suitable to compare behavior of `org-babel
Ihor Radchenko writes:
> I am not sure if it is an actual issue.
>
> Note that (_u can be interpreted as a subscript.
> Org prioritises subscript over underline.
>
> Looking at the code:
>
> (?_ (or (and (memq 'subscript restriction)
> (org-element-subscript-parser))
> (and (memq '
Juan Manuel Macías writes:
> I don't know if this is a known issue...
>
> Consider the text:
>
> (_underline_)
I am not sure if it is an actual issue.
Note that (_u can be interpreted as a subscript.
Org prioritises subscript over underline.
Looking at the code:
(?_ (or (and (memq 'subscript
Juan Manuel Macías writes:
> If I do M-! (occur org-match-substring-regexp)
>
> I get:
>
> 10:(_underline_)
> 22:(_underline_ text)
Well, in my case the temporary workaround was to force super/subscripts
with braces:
#+begin_src emacs-lisp
(defun my-org-element-subscript-with-braces-
Hi,
Kyle Meyer writes:
Rudolf Adamkovič writes:
Reproduction steps:
1. start "emacs -Q"
2. type "C-x C-f" and "test.org" and RET
3. type the following:
- one
two
- three
four
4. mark all with "C-x h"
5. type "M-q" to fill
Actual:
- one
two
- three four
Expected:
- one two
Hi all,
I don't know if this is a known issue...
Consider the text:
(_underline_)
When exported to LaTeX we get:
(\textsubscript{underline}\_)
And to HTML:
(underline_)
The same result with:
(_underline_ text)
LaTeX:
(\textsubscript{underline}\_ text)
But this:
(this word is _underline
>>> "TC" == Tim Cross writes:
> Uwe Brauer writes:
> For problem 1, I suspect you will need to either change the date format
> or tell org what the date format is. It won't work trying to sort
> numerically as those values are not really numerical values. The date
> format you currently have I
>>> "TC" == Tim Cross writes:
> Uwe Brauer writes:
>> [[S/MIME Signed Part:Undecided]]
>>
>>
>> * Problem 1
>>
>> I imported this column from a CVS file, so the date format was already
>> chosen.
>>
>> | Date |
>> ||
>> | 05.05.2020 |
>> | 07.01.2021 |
>> | 07.01.2021 |
>
20 matches
Mail list logo
