Leo Butler writes:
> On Sat, Sep 02 2023, Ihor Radchenko wrote:
>
>> Lockywolf writes:
>>
>>> At the moment, ob-maxima has a straightforward way of evaluating
>>> babel blocks,
>>>
>>> #+begin_src shell
>>> maxima --very-quiet -r batchload\(\"/tmp/ob-maximaFOOBAR.mac\"\)\$
>>> #+end_src
>>>
Ilya Chernyshov writes:
> Recently, I implemented multi-day views feature for org-timeblock. You
> can now choose the number of days (1-7) displayed via command
> org-timeblock-switch-view. Here's a screenshot:
>
>
Finally I can upload some usable code here, in this case to be able to
load and manage fonts for languages with non-Latin scripts, through
babel and fontspec (in LuaLaTeX). It is an attempt to simplify from Org
the multiform syntax of babel + fontspec. Of course, it is more limited,
but for
On Sat, Sep 02 2023, Ihor Radchenko wrote:
> Lockywolf writes:
>
>> At the moment, ob-maxima has a straightforward way of evaluating
>> babel blocks,
>>
>> #+begin_src shell
>> maxima --very-quiet -r batchload\(\"/tmp/ob-maximaFOOBAR.mac\"\)\$
>> #+end_src
>> (line 87 of ob-maxima.el),
>>
>> I
On Sat, Sep 02 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> I think that your request may be handled by one of two improvements:
>>
>> 1. Implement session support in ob-maxima.el; and
>> 2. Many of the design decisions in the existing ob-maxima code should be
>> customizable.
>
>> I
On 2023-09-02 09:10, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> - Even if we made "&" mandatory, it would not really solve the quoting
>> problem, since the parser is rather hacky and other quoting and
>> context issues would still be there.
>
> But at this point you are more familiar
On 2023-09-02 09:10, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> This all calls for a proper parser, based on peg or bovine or whatever.
>> Hopefully that parser would still keep backward compatibility, but
>> that's probably wishful thinking.
>
> Backward compatibility will be easy - just
Hi
I am sorry, I don't know the appropriate terminology.
Could be used
*** END
or a different special string, to end any headline scope? Like an "end
parenthesis" for the headline just above it.
Maybe in this way, all headlines would be the same: if the special
string
On 01/09/2023 16:04, Ihor Radchenko wrote:
Max Nikulin writes:
However I do not mind to have an easy way to delegate URI from :export
function to the link transcoder of active export backend.
Just make the :export function return nil.
I missed this feature, but anyway it does not work as
Ihor Radchenko writes:
> Andrea Lazzarini writes:
>
>> I was busy with work and had less time to focus on this, sorry!
>
> No problem. Just wanted to make sure that this thread did not fall
> through the cracks.
It has been two months since the last message here.
If you encounter any
Ihor Radchenko writes:
> Then, ox.el and other link processing code, when encountering a link
> type that is not registered, will fall back to searching "fuzzy" link.
>
> So, export, and following the link should not be affected.
This resolves my worry — thank you!
> There might be caveats
Tom Gillespie writes:
> My suggestion is as follows. Schemes/prefixes defined by the
> #+link: keyword can be used without surrounding syntax markers
> but may not contain spaces etc.
> ... To support this Org parsers
> should always parse prefix:suffix as a _putative_ link which
> must then be
Jens Lechtenboerger writes:
> On 2023-09-01, Ihor Radchenko wrote:
>
>> In theory, we might change the parser to treat anything like foo:bar or
>> or [[foo:bar]] as a link with "foo" protocol and "bar" URI.
>> And introduce [[::fig:something]] to allow explicit internal links.
>> But, despite
"Dr. Arne Babenhauserheide" writes:
>> May you elaborate about what is going to be broken?
>
> I have many links where I use <> along with
> [[sec:spielbeispiel]], often along with
> @@latex:\phantomsection\label{sec:spielbeispiel}@@ to enable reliable
> inline linking inside org-mode and across
Leo Butler writes:
> I think that your request may be handled by one of two improvements:
>
> 1. Implement session support in ob-maxima.el; and
> 2. Many of the design decisions in the existing ob-maxima code should be
> customizable.
> I am attaching a patch to address 2. Please try it out, I
Jens Schmidt writes:
> TL;DR:
>
> - I think we cannot make "&" mandatory because of backward compatibility.
Sorry for the confusion. I did not mean that "&" should be mandatory,
just that "&" might make it easier to avoid a need to escape things. So,
it could be used _instead_ of escaping.
> -
Lockywolf writes:
> At the moment, ob-maxima has a straightforward way of evaluating
> babel blocks,
>
> #+begin_src shell
> maxima --very-quiet -r batchload\(\"/tmp/ob-maximaFOOBAR.mac\"\)\$
> #+end_src
> (line 87 of ob-maxima.el),
>
> I suggest replacing batchload with batch(), and changing
17 matches
Mail list logo
