Hello Sterling,
* Sterling Hooten [2022-12-14 08:39]:
> I'm trying to clone Lotus notes in Org mode.
What features do you try to implement?
Or are you trying to import your own notes into the Org?
Org does not have functions of sharing, while it could have,
it doesn't, it is not considered imp
Jean Louis writes:
> * Sterling Hooten [2022-12-14 08:39]:
>> I'm trying to clone Lotus notes in Org mode.
>
> What features do you try to implement?
>
> Or are you trying to import your own notes into the Org?
>
> Org does not have functions of sharing, while it could have,
> it doesn't, it is
When I evaluate erroneous code of an Elisp code block like
#+BEGIN_SRC elisp
(x)
#+END_SRC
I see the error message ("Symbol's function definition is void: x") in
the minibuffer (and in the *Messages* buffer).
This is not the case with Scheme code blocks; evaluating the code block
#+BEGIN_SRC sc
On 15/12/2022 11:17, Stefan Monnier wrote:
Max Nikulin [2022-12-14 23:02:53] wrote:
Completion failure for "org-to" happened because result of
`register-definition-prefixes' calls is not considered as options. I am
aware that it may give false positives, but I still believe they should
be added.
El 2022-12-01 04:12, alain.coch...@unistra.fr escribió:
> With the 9.5.5 version
>
> Org mode version 9.5.5 (9.5.5-g8ef620 @
> /home/cochard/.emacs.d/elpa/org-9.5.5/)
>
> What I have in Info is
>
> The Org Manual
> **
>
> This manual is for Org version 9.5.
>
>
Message was on topic as it provided design directions on how to avoid
properties, without technical actual program.
Numerous people will express numerous directions on how specific
problem may be solved.
Take the life as it is.
I don't appreciate this kind of slap and wining about nothing!
* I
Max Nikulin writes:
> I have impression that there is no recipe how to reproduce this bug yet,
> just reports that people have faced it. So aspects of autoload may be
> considered as a part of brainstorm.
>
> Other ideas when built-in Org version may be loaded too early:
> - restoring previous
Jean Louis writes:
> Message was on topic as it provided design directions on how to avoid
> properties, without technical actual program.
>
> Numerous people will express numerous directions on how specific
> problem may be solved.
>
> Take the life as it is.
I agree that your message is on to
Reproduction steps:
#+BEGIN_SRC bash :results list
echo 1
echo 2
echo 3
#+END_SRC
Actual:
#+RESULTS:
- (1)
- (2)
- (3)
Expected:
#+RESULTS:
- 1
- 2
- 3
Rudy
--
"Logic is a science of the necessary laws of thought, without which no
employment of the understanding and the reason takes place."
Rudolf Adamkovič writes:
> Reproduction steps:
>
> #+BEGIN_SRC bash :results list
> echo 1
> echo 2
> echo 3
> #+END_SRC
> ...
Confirmed.
It appears to be present at least since Org shipped with Emacs 27.
Wondering how nobody noticed...
We really need more tests.
--
Ihor Radchenko // yantar92
Just to remind you the encoding warning does not occur with the same files
using the emacs 28.1 with orgmode 9.52 included. The characters that
trigger the warning are ones that are not found in UTF-8 and since I do a
lot of editing of web documents and do not correct them until final
output. org
Org version is 9.5.2; emacs version is 27.1.
The manual does not indicate that underscores need to be escaped in
links (and they can't be, as far as I can tell). The latex and html
exporters interpret them as the start of a subscript.
Leo
#+AUTHOR: Leo Butler
#+TITLE: Bug in processing underscor
marcin> One question I'd ask is: how important a legible diff is to
you? I keep my Org files in Git, too, but if /I/ know what was
changed, I just don't care about diff going nuts and I treat it as
(more or less) Git's internal implementation detail.
for org, i mostly use git for reviewing change
On 17/12/22 11:32, Leo Butler wrote:
Org version is 9.5.2; emacs version is 27.1.
The manual does not indicate that underscores need to be escaped in
links (and they can't be, as far as I can tell). The latex and html
exporters interpret them as the start of a subscript.
Leo
By default undersc
Hi Ihor,
Chiming in here with a slight variant on what
others have said. Best!
Tom
I don't think this should be handled at the syntactic
layer at all. The empty string block language should
be syntactically valid with any special behavior
needed being handled later.
Linters could treat it as a
In my opinion the function: (org-heading-components) shall not error,
no matter if it is called outside of the heading, it could still
return nil values if it is outside of the header.
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
looking-at(nil)
org-heading-components()
16 matches
Mail list logo
