In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to the
"very instructive post by Pete Phillips" now directs to the defunct
gmane.org. I think I tracked down the post it is supposed to link to, so I
don't want others to have to do this work again:
https://lists.gnu.org/archive/htm
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
---
org-table-iterate function not working on multiline #+TBLFM
| 1 | 2 |
| | |
| | |
#+TBLFM: @2$1..@2$2=@1
#+TBLFM: @3$1..@3$2=@2
I have to stroke C-c C-c on each line of #+TBLFM
...@gmail.com writes:
> org-table-iterate function not working on multiline #+TBLFM
>
>
>
> | 1 | 2 |
> | | |
> | | |
>
> #+TBLFM: @2$1..@2$2=@1
> #+TBLFM: @3$1..@3$2=@2
>
> I have to stroke C-c C-c on each line of #+TBLFM
You have to write
| 1 | 2 |
| | |
| | |
#
Hi Matt,
I made this change, because I found the previous way jarring. The window
with the selection information showed up in different places depending on
what the current window setup is. With the new implementation, the info
window is always in the same predictable place. After the selection
Hi Vladimir,
On Mon, 21 Oct 2019 at 03:21, Vladimir Nikishkin
wrote:
>
> Can we replace the (set) on line 177 of ob-scheme.el with the following
> form:
> (setq result (if output
> (let ((g-r-o (geiser-eval--retort-output ret)))
> (if g-r-o
>
On Mon, 21 Oct 2019 at 15:16, Vladimir Nikishkin
wrote:
> Yeah. The "output" is not the result of geiser's elisp functions, as far
> as I understand, it comes from comint, which reads it from a scheme
> interpreter, and is expected to be formatted specifically to be fed into
> geiser-eval--retort
Joshua Meyers writes:
> In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to
> the "very instructive post by Pete Phillips" now directs to the
> defunct gmane.org. I think I tracked down the post it is supposed
> to link to, so I don't want others to have to do this work again:
>
On 21/10/2019 23:24, Vladimir Nikishkin wrote:
> Well, checking for "output" doesn't seem to be useful any way, since
> "output" is never 'nil.
>
> Regarding the fact that the error should be reported to the geiser
> mailing list, that's entirely true. The problem is that the person who
> would
