Re: [O] Bug: Problems with ob-scheme in geiser-eval--retort-output [9.2.6 (9.2.6-4-ge30905-elpa @ /home/lockywolf/.emacs.d/elpa/org-20191021/)]

[Vladimir Nikishkin]

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 be responsible for this error would be me. :) At least for the
> chibi-scheme part.
> 
> I don't think that having a few extra checks on the org/geiser interface
> is bad, especially there is also comint coming into play. I can imagine
> valid reasons when "output" is not a valid serialized scheme expression.
> 
> On 21/10/2019 22:46, Neil Jerram wrote:
>> 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-output by the geiser scheme functions (running
>> inside a scheme interpreter).
>>
>> So "output" is never 'nil, because comint, when scheme produces some
>> rubbish, just makes it an empty string, which is not 'nil.
>>
>> Then, "output" is expected to be "retorted" back from a serialized
>> scheme expression into an elisp expression by
>> geiser-eval--retort-output. And this actually may and produce a 'nil,
>> but there is no check for it.
>>
>> So, again, both of the geiser steps (namely, (a) serializing a sexp in
>> scheme, and (b) de-serializing it in geiser-eval--retort-output) may
>> fail.
>>
>>
>> I agree that it's fragile for geiser/scheme to output a sexp that it
>> hopes geiser/elisp will be able to read back.  (I'm guilty of doing that
>> in the past too!)
>>
>> Do you have a specific example of that?  It feels like the right thing
>> to do would be to report that to the Geiser list, as this could and
>> should be fixed entirely within the Geiser code.
>>   
>>
>>
>> Yes, I have seen this going on, actually quite a lot, because both
>> geiser and different scheme interpreters are in constant development and
>> get broken every other day.
>>
>>
>> I use Org with Guile 2.2.3 (via Geiser), and it seems a pretty stable
>> setup to me.
>>  
>> Best wishes,
>>      Neil
>>  


A particularl example could be, perhaps, when an interpreter crashes and
produces something like "Segmentation fault", which is not a valid
geiser-sexp.


pEpkey.asc
Description: application/pgp-keys

Re: [O] Bug Report: Broken Link in Worg

[Nick Dokos]

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:
> https://lists.gnu.org/archive/html/emacs-orgmode/2007-12/msg00281.html
>

You can go one step further and actually fix it in the worg page -
worg is user-editable: https://orgmode.org/worg/index.html#org218100b

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] Bug: Problems with ob-scheme in geiser-eval--retort-output [9.2.6 (9.2.6-4-ge30905-elpa @ /home/lockywolf/.emacs.d/elpa/org-20191021/)]

[Neil Jerram]

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-output by the geiser scheme functions (running
> inside a scheme interpreter).
>
> So "output" is never 'nil, because comint, when scheme produces some
> rubbish, just makes it an empty string, which is not 'nil.
>
> Then, "output" is expected to be "retorted" back from a serialized
> scheme expression into an elisp expression by
> geiser-eval--retort-output. And this actually may and produce a 'nil,
> but there is no check for it.
>
> So, again, both of the geiser steps (namely, (a) serializing a sexp in
> scheme, and (b) de-serializing it in geiser-eval--retort-output) may fail.
>

I agree that it's fragile for geiser/scheme to output a sexp that it hopes
geiser/elisp will be able to read back.  (I'm guilty of doing that in the
past too!)

Do you have a specific example of that?  It feels like the right thing to
do would be to report that to the Geiser list, as this could and should be
fixed entirely within the Geiser code.


>
> Yes, I have seen this going on, actually quite a lot, because both
> geiser and different scheme interpreters are in constant development and
> get broken every other day.
>

I use Org with Guile 2.2.3 (via Geiser), and it seems a pretty stable setup
to me.

Best wishes,
 Neil

Re: [O] Bug: Problems with ob-scheme in geiser-eval--retort-output [9.2.6 (9.2.6-4-ge30905-elpa @ /home/lockywolf/.emacs.d/elpa/org-20191021/)]

[Neil Jerram]

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
>  g-r-o
>  "Geiser-eval--retort-output returned nil.\nThe
> interpreter produced no output\nor there is a bug in geiser (likely!)"))
> (geiser-eval--retort-result-str ret "")
>
> I am not super sure about what's going on there, but I think that output
> can never be an empty list, because in the worst case it is an empty
> string.
> (But I wouldn't vouch for this.)
>

Can you explain more?  Have you seen cases
where (geiser-eval--retort-output ret) returns nil, even though you say
just above that it can never do that?

Best wishes,
Neil

Re: [O] org-fast-todo-selection window behaviour?

[Carsten Dominik]

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 is
done, the old window setup is restored to exactly what it was

Carsten

On Sun, Oct 20, 2019 at 8:46 PM Matt Price  wrote:

> I've recently noticed a slightly frustrating behavour on the part of
> org-todo that I think is new and maybe was introduced in mid-August with
>
> f1c030bed54737319aeb1d592e3340d6a48cea3a
>
> In a split frame,calling org-todo with org-use-fast-todo-selection
> enabled, ~C-c C-t~ now calls ~delete-other-windows~ before popping up the
> org-todo keywords window.  Is this necessary? I find this behaviour
> visually confusing and distracting, and a slowdown to my workflow.  Would
> it make sense to introduce some kind of defcustom for this? For now I'm
> just commenting out line 10614 of org.el, but if others want to be able to
> customize the behaviour I will submit a patch.
>
> Maybe there's a reason delete-other-window is necessary, but i don't see
> it in the commit message nor immediately in the other parts of this
> otherwise very well-documented commit
>
> Thanks!
>
>

Re: [O] org-table-iterate function not working on multiline #+TBLFM

[Loris Bennett]

...@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 |
  |   |   |
  |   |   |
  #+TBLFM: @2$1..@2$2=@1::@3$1..@3$2=@2

Cheers,

Loris

-- 
This signature is currently under construction.

[O] org-table-iterate function not working on multiline #+TBLFM

[11111111111]

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

[O] Bug: python src var error [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]

[Claire Chambers]

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.


Hello! this webpage: https://orgmode.org/manual/var.html says that
unordered lists have nested elements ignored, but running the same code
snippet gives "| simple | (unordered (not) (nested)) |
| list   ||", not  "| simple | list |". 


Emacs  : GNU Emacs 26.2 (build 1, x86_64-apple-darwin18.2.0, NS appkit-1671.20 
Version 10.14.3 (Build 18D109))
of 2019-04-12
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ 
/Applications/Emacs.app/Contents/Resources/lisp/org/)

current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-html-format-inlinetask-function 'org-html-format-inlinetask-default-function
org-src-tab-acts-natively t
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-agenda-files '("~/Documents/org/school.org" "~/Documents/org/home.org")
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-reveal-start-hook '(org-decrypt-entry)
org-startup-folded 'overview
org-mode-hook '(yas-minor-mode org-bullets-mode linum-mode turn-on-flyspell 
visual-line-mode
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-show-block-all append local]
   5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all 
append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-startup-indented t
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
org-from-is-user-regexp "|\\"
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-babel-pre-tangle-hook '(save-buffer)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
org-hide-leading-stars t
org-babel-load-languages '((emacs-lisp . t) (python . t))
org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS 
WIDTH)"]
org-ellipsis " ..."
org-occur-hook '(org-first-headline-recenter)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
org-todo-keywords '((sequence "TODO(t)" "NEXT(n)" "|" "DONE(d)")
 (sequence "WAITING(w@/!)" "HOLD(h@/!)" "|" 
"CANCELLED(c@/!)" "PHONE" "MEETING"))
org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
org-babel-tangle-lang-exts '(("python" . "py") ("emacs-lisp" . "el") ("elisp" . 
"el"))
org-confirm-shell-link-function 'yes-or-no-p
org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow 
org-rmail-open :store org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow org-irc-visit :store org-irc-store-link)
   ("info" :follow org-info-open :export org-info-export 
:store org-info-store-link)
   ("gnus" :follow org-gnus-open :store org-gnus-store-link)
   ("docview" :follow org-docview-open :export 
org-docview-export :store org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store 
org-bibtex-store-link)
   ("bbdb" :follow org-bbdb-open :export org-bbdb-export 
:complete org-bbdb-complete-link
:store org-bbdb-store-link)
   ("w3m" :store org-w3m-store-link) ("file+sys") 
("file+emacs")
   ("doi" :follow org--open-doi-link) ("elisp" :follow 
org--open-elisp-link)
   ("file" :complete org-file-complete-link)
   ("ftp" :follow (lambda (path) (browse-url (concat "ftp:" 
path
   ("help" :follow org--open-help-link)
   ("http" :follow (lambda (path) (browse-url (concat 
"http:" path
   ("https" :follow (lambda (path) (browse-url (concat 
"https:" path
   ("mailto" :follow (lambda (path) (browse-url (concat 
"mailto:; path

[O] Bug Report: Broken Link in Worg

[Joshua Meyers]

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/html/emacs-orgmode/2007-12/msg00281.html

Best,
Joshua