Currently, evaluating the Org-mode source block
#+NAME: bug
#+BEGIN_SRC octave :exports results
["one"; "two"; "three"]
#+END_SRC
gives
#+RESULTS: bug
: ottnwheor e e
Substituting ~fprintf~ in ~org-babel-octave-wrapper-method~ with ~fdisp~
changes the output to
#+NAME: bug
#+BEGIN_SRC octav
emacs 25.1 does not have this function. this error occurs upon
find-file on an org file in org 9.5.
File mode specification error: (void-function file-attribute-inode-number)
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
manual> These
commands can also be used in ‘*grep*’ buffers, where the hyperlinks are
search matches rather than error messages (*note Grep Searching::).
--- (info "(emacs) Compilation Mode")
it is likely common to have grep and compilation mode open at the same
time. i think this is like your mu
[as an example, i should not have brought up the follow mode example
at all. it seems to have only confused readers. i was trying to
forestall any suggestions that follow-mode exists and can do the job
that next-error can is all. it can't do the same job.]
On 12/19/21, Samuel Wales wrote:
> On
On 12/19/21, Ihor Radchenko wrote:
> multiple agenda views is not an uncommon workflow. You may have daily
i think this is a strong objection. multiple simultaneous agenda
views seems to sink my suggestion.
can one have multiple simultaneous c-c / buffers? and multiple
grep/occur/compilation s
Samuel Wales writes:
> btw, if anybody has difficulty understanding why i mention a bug or
> suggest a feature [such as why anbydoy would want it], please feel
> free to say so, otherwise i don't know that that is the case. [please
> go easy on me though.]
This is a difficult query. There are m
Michael Eliachevitch writes:
> I found a potential bug in org which I can reproduce with a
> minimal configuration.
Can you try the attached patch?
Best,
Ihor
>From c0e5f708a2b027ca701267bca383d367b7fee51f Mon Sep 17 00:00:00 2001
Message-Id:
From: Ihor Radchenko
Date: Sun, 19 Dec 2021 21:
"Mailbox.org" writes:
> --text follows this line--
>
> What exactly did you do?
> I include a source code block for shell in an org-files.
> Example:
>
> #+begin_src shell
> foo
> #+end_src
> Within that source code block I type RET (Return)
FYI, I am unable to reproduce this.
Best,
Ihor
Tak Kunihiro writes:
> I confirm that there still is the problem with org-table on Emacs
> 28.0.90 pretest with org-version 9.5.1.
>
> Here is a recipe to reproduce the problem. I still have to stick to
> 26.3.
I was able to reproduce. Can you try the attached fix?
Best,
Ihor
>From 7b1a7d43e0
Lele Gaifax writes:
> I couldn't test yet, but I saw a couple of other glitches, sorry for not
> noticing first.
Thanks for the proof reading.
I updated the patch accordingly.
Best,
Ihor
>From 557e7cec6dd22b09468b82650feed2020f97d781 Mon Sep 17 00:00:00 2001
Message-Id: <557e7cec6dd22b09468b82
Kaushal Modi writes:
>> On latest main, your example file is exported without any warnings.
>>
>
> I just verified that. Also, I did not even need to add
> `(org-element-cache-reset)' in `org-hugo--get-pre-processed-buffer' after
> the `(insert ..)' in the temp buffer.
>
> Is that expected?
Depe
Karl Fogel writes:
> Should we just remove `org-truely-invisible-p'? Or at least
> correct the spelling of its name ("truely" should be "truly")?
I feel slightly reluctant about removal. If nothing, this function can
be a reminder about visible-mode and keeping it has little downside.
Though i
Sorry for delay. I expected that a next step with inline raw AST
fragments would be easier, but I have got working example for parser
tests grouped in single file earlier.
Certainly org files may be source for parser tests. They are readable
enough to be convenient for developers and, I hope,
13 matches
Mail list logo
