From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Orgalist notes
Date: Mon, 07 May 2018 11:13:53 +0200 [thread overview]
Message-ID: <87in7zbzfy.fsf@len.workgroup> (raw)
In-Reply-To: <87k1sh81f8.fsf@nicolasgoaziou.fr>
Hi Nicolas,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [2018-05-06; 13:32]:
> Gregor Zattler <telegraph@gmx.net> writes:
>
>> With org-mode in the load-path, the line breaks happen for all
>> lines not only the first one. But one has to (require 'org) in
>> order for M-RET to work. This is no problem for me, since I work
>> with org-mode all the time, but is this intended?
>
> No, it is not intended. Orgalist 1.6 (to be released tomorrow) will
> require Org right from the start.
This works now with bullet and numbered lists when called in a
non-configured emacs session. Thanks.
>> In my highly customized emacs I get line breaks but M-RET gives
>>
>> 1. jesdgf oigjovgjis uh urh udrhfesgh ourhes ouh ouhroe uhos ho
>> hg uirehui shgourheoug hhsou hogush oguhuishughsoieghoudrhes
>> uhguhdsh ghourhg
>>
>> orgalist-insert-item: Wrong type argument: integer-or-marker-p, nil
[...]
>> Could you give me a hint on how to debug this?
>
> Please use M-x toggle-debug-on-error and report the backtrace here.
> Loading an un-compiled Orgalist is better.
1. rzhe juhgdhjvhj vghfjs y rvgfhjxd bvjxdbv mh vxnbxgbfvghg drgh
djhxcjhbnjdfjhvgjhf jhfhjghfj hfjM-RET
gives:
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
org-list-insert-item(1504 ((1397 0 "1. " nil nil nil 1505)) ((1397)) nil nil)
(setq struct (org-list-insert-item (point) struct prevs checkbox desc))
(let* ((struct (save-excursion (goto-char item\?) (orgalist--struct))) (prevs (org-list-prevs-alist struct)) (desc (and (eq 'descriptive (org-list-get-list-type item\? struct prevs)) " :: "))) (setq struct (org-list-insert-item (point) struct prevs checkbox desc)) (org-list-write-struct struct (org-list-parents-alist struct)) (looking-at orgalist--item-re) (goto-char (if (and (match-beginning 4) (let ((save-match-data-internal (match-data))) (unwind-protect (progn (string-match "\\." (match-string 1))) (set-match-data save-match-data-internal 'evaporate)))) (match-beginning 4) (match-end 0))) (if desc (progn (backward-char 1))))
(let ((item\? (orgalist--in-item-p))) (if item\? nil (user-error "Not in a list")) (let* ((struct (save-excursion (goto-char item\?) (orgalist--struct))) (prevs (org-list-prevs-alist struct)) (desc (and (eq 'descriptive (org-list-get-list-type item\? struct prevs)) " :: "))) (setq struct (org-list-insert-item (point) struct prevs checkbox desc)) (org-list-write-struct struct (org-list-parents-alist struct)) (looking-at orgalist--item-re) (goto-char (if (and (match-beginning 4) (let ((save-match-data-internal (match-data))) (unwind-protect (progn (string-match "\\." (match-string 1))) (set-match-data save-match-data-internal 'evaporate)))) (match-beginning 4) (match-end 0))) (if desc (progn (backward-char 1)))))
orgalist-insert-item(nil)
funcall-interactively(orgalist-insert-item nil)
call-interactively(orgalist-insert-item nil nil)
command-execute(orgalist-insert-item)
I have no clue how to read this.
Thanks for looking into this, Gregor
next prev parent reply other threads:[~2018-05-07 9:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 23:21 Orgalist notes Eric Abrahamsen
2018-05-03 23:44 ` Eric Abrahamsen
2018-05-04 5:53 ` Eric S Fraga
2018-05-04 6:45 ` Eric Abrahamsen
2018-05-04 8:14 ` Alan Schmitt
2018-05-04 8:50 ` Eric S Fraga
2018-05-04 16:44 ` Eric Abrahamsen
2018-05-04 16:55 ` Eric S Fraga
2018-05-05 11:37 ` Gregor Zattler
2018-05-05 12:50 ` Nicolas Goaziou
2018-05-05 23:55 ` Eric Abrahamsen
2018-05-06 7:30 ` Nicolas Goaziou
2018-05-06 10:43 ` Gregor Zattler
2018-05-06 11:32 ` Nicolas Goaziou
2018-05-07 9:13 ` Gregor Zattler [this message]
2018-05-07 12:37 ` Nicolas Goaziou
2018-05-07 16:57 ` Gregor Zattler
[not found] ` <87lgcvv0aw.fsf@nicolasgoaziou.fr>
2018-05-07 20:22 ` Gregor Zattler
2018-05-07 20:29 ` Nicolas Goaziou
2018-05-08 18:32 ` Gregor Zattler
2018-05-06 14:34 ` Bernt Hansen
2018-05-06 16:04 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in7zbzfy.fsf@len.workgroup \
--to=telegraph@gmx.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).