My current solution (which already differs from the last one I posted
here...) is here:
https://github.com/jkitchin/scimax/blob/master/scimax-org-src-blocks.el#L61
It is more selective, and only changes the syntax inside these src
blocks:
"jupyter-python" "python" "emacs-lisp"
and does not chan
I believe this has been mentioned in passing in this thread but I'll
repeat just in case: Unless you are working with xml or HTML in your org
documents, and even then, having these two lines in your org
configuration (e.g. org-mode-hook):
(modify-syntax-entry ?< ".")
(modify-syntax-entry ?
hi, all.
Arthur Miller wrote:
> Well, in this case it is a tool deficiency, if you don't like gt, than use
> use "greater-than", it can't be more clear intent? After all, this is a lisp,
> and
> '>' is just a symbol name, like any other. For the inclusion of code, yes, but
> that is why we have
Tim Cross writes:
> Arthur Miller writes:
>
>> I haven't tested the updated version of JK's proposal, but looking at the
>> source
>> it seems to be a tad bit resource heavy. If it isn't a hassle for the OP to
>> use
>> aliases like lt, gt or similar, I would suggest that either using macros o
Arthur Miller writes:
> I haven't tested the updated version of JK's proposal, but looking at the
> source
> it seems to be a tad bit resource heavy. If it isn't a hassle for the OP to
> use
> aliases like lt, gt or similar, I would suggest that either using macros or
> simple defalias to ren
Tim Cross writes:
> John Kitchin writes:
>
>> My previous solution seems like it stopped working for some reason. Here is
>> a new version that "should" only change syntax
>> inside src-blocks, but not inside strings.
>>
>> It looks like this does not impact html blocks, or xml blocks.
>>
>> It
John Kitchin writes:
> My previous solution seems like it stopped working for some reason. Here is a
> new version that "should" only change syntax
> inside src-blocks, but not inside strings.
>
> It looks like this does not impact html blocks, or xml blocks.
>
> It is probably possible to mak
My previous solution seems like it stopped working for some reason. Here is
a new version that "should" only change syntax inside src-blocks, but not
inside strings.
It looks like this does not impact html blocks, or xml blocks.
It is probably possible to make it mode specific if needed.
(defun
I think what is happening here is that org is bumping up against
fundamental design limitations of Emacs. In basic terms, much of Emacs'
underlying design is based on an assumption that a file only has a
single major mode. Org works hard to get around this limitation, but it
comes with cost - usu
That is probably a matter of opinion.
If you use angle brackets as delimiters, e.g. in html, xml in src-blocks,
then the current syntax definition makes sense because you can use them
to find open and closing brackets, navigate them, etc.. If you don't use
those, it makes less sense, and maybe isn
Thank you, John.
I will give it a try.
However, is this a bug that should be fixed within org source code?
Charlie Millar
On 9/2/21 2:24 PM, John Kitchin wrote:
I think this issue is described in
https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch.
There
11 matches
Mail list logo
