Kyle Meyer writes:
> case is still available under the cl- prefix. If you wanted to use it
> in 73c99bf42 (org-plot.el: add utility functions for range,ticks), I
> don't see a reason not to use it now.
I tend to use pcase over cl-case (since it's completely built in, i.e.
no (require 'cl-lib)
Hmm, I tried on master (9140a712f) and maint (97f1d8e34) and
can't
trigger the issue.
Am I overlooking some detail?
Ok, I managed to narrow it down to a particular aspect of my
init file.
I modify the syntax table for text modes to handle the meaning of
some characters in French. In fact,
Greg,
I just did a quick test and I cannot reproduce this, the tabs remain on
entering, modifying and exiting block-edit mode.
One question: do you see "Makefile" as the mode when you are editing the
source block? Otherwise I imagine tab-to-space conversion might be taking
place.
--Diego
On We
Diego,
thanks for looking at it. i apologize for not having looked at an
"emacs -Q" (and, thanks to Ihor for, a few days ago, having pointed out
how to "emacs -Q" with one's "normal" org version).
: emacs -Q -L ~/.emacs.d/elpa/org-20201012/ -l org
exhibits *half* of the behavior i am mentioning
On 22.12.20 22:20, Kyle Meyer wrote:
Vladislav Glinsky writes:
Please note that changes from this patch cause clipping of popups with
language labels (pre.src:before).
Thanks for reporting and sorry for the slow reply. As far as I can
tell, this was fixed by Fatih Aydin in 5ee39c352 (ox-html:
Bump this thread, hi, Nicolas, any thoughts or update about this?
stardiviner writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> I have following minimal testing code:
>
> #+begin_src emacs-lisp
> (defun org-link-beautify (start end path bracketp)
> "Display icon for the Org l
Resending as plain-text ... If somebody could point me in the direction of
the code that might be responsible for this, I'll try to take a look.
If the following org file is exported as HTML, any *strong* markup for words
at the beginning or the end of the input string are ignored. (I ha
Hello, a possible dirty solution could be defining the macro with two
Unicode zero-width spaces (u+200b):
#+MACRO: quote (eval (concat "@@html:“@@" "\u200B"
$1 "\u200B" "@@html:”@@"))
Regards,
Juan Manuel
m27315 writes:
> Resending as plain-text ... If somebody could point me in the direct
You're welcome. Some time ago I had a similar problem with a LaTeX
command with arguments that I wanted to include in a macro. Since the
character U+200b is a kind of "ghost space", it can act as an "invisible
barrier" between the emphasis marks and the characters that precede or
follow them. An em
TEC writes:
> Kyle Meyer writes:
>
>> case is still available under the cl- prefix. If you wanted to use it
>> in 73c99bf42 (org-plot.el: add utility functions for range,ticks), I
>> don't see a reason not to use it now.
>
> I tend to use pcase over cl-case (since it's completely built in, i.e.
Kyle Meyer writes:
> Regardless of what you tend to use, you used "case" here in 73c99bf42;
> the minimal fix is to add a cl- prefix, and any other switch with the
> justification that "case is obsolete" is likely to raise a reviewer's
> eyebrow.
This makes sense.
> cl-case isn't in cl-lib, an
> in case not obvious, i am suggesting a nil value for org adapt indentation.
> thus no physical indentation of all lines including planning lines.
> i'd even suggest no physical indentation as default for example and
> source blocks, but that is a can of worms.
I know that this is a can of worms,
Hi
When installing the org 9.4.4 I noticed that the defintion of org-odt-data-dir
isn't correct.
It is:
(defvar org-odt-data-dir (expand-file-name "../../etc/" org-odt-lib-dir)
It should be:
(defvar org-odt-data-dir (expand-file-name "../../etc/org/" org-odt-lib-dir)
To reproduce,
make
"Victor A. Stoichita" writes:
> I modify the syntax table for text modes to handle the meaning of
> some characters in French. In fact, te actual modification doesn’t
> seem to matter. The following is enough to trigger the described
> behavior:
>
> --8<---cut here---st
TEC writes:
> Kyle Meyer writes:
>
>> recent org-plot example from 8d5122fc5:
>> [...]
>> That could be rewritten as [...]
>
> Would you like me to bundle that change in somewhere?
In my view it's fine to leave it as is (it's just an example that was
fresh in my mind), but of course feel free to
Tom,
> The other reason I think this is a good idea is because I have been
> working on a formal grammar for the org syntax, and everything would
> be SO much simpler about the implementation after the first pass parse
> if the canonical representation of an Org file did not allow
> significant wh
> possibly i'm misunderstanding, but my sense is that the value of org
> adapt indentation doesn't change what you might actually find ("in a
> .org file in the wild"). so, whatever its value, your grammar would
> have to deal with all cases?
Yep, we can't magically change all the files out in th
I haven't figured it out yet, but there seems to be a bug between Org
and Org-Journal. Both recently got updated to the latest versions and
then I noticed that org-deadline would have a problem with the version
number. I believe that Org-Journal installs a function into a hook for
(in)visible tex
18 matches
Mail list logo
