emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Orgalist notes
Date: Sun, 06 May 2018 12:43:02 +0200	[thread overview]
Message-ID: <87bmdtkqtl.fsf@len.workgroup> (raw)
In-Reply-To: <87sh754q02.fsf@ericabrahamsen.net>

Hi Eric, Nicolas,
* Eric Abrahamsen <eric@ericabrahamsen.net> [2018-05-05; 16:55]:
> - And before I get tired of the experiment, here's the same thing with
>  a numbered list.
> - Oh damn, I hit M-RET, and the numbered list turned into an unnumbered
>   list.

with this:
emacs-snapshot -Q  --debug-init  -l /home/grfz/.emacs.d/elpa-27.0/orgalist-1.5/orgalist.el   -f compose-mail  --eval "(progn (orgalist-mode t) (end-of-buffer) (newline) (newline))"


I get


1. ha fkj hdhf kjh kdjfh kdjsh gjhdlkj ghkjdsgh dj ljgh kjdh kjhvgfkj
   hdgkjhkjh djhg kjdhf kjhdkjghf kdhödgkhödkj hödj öh ödfkj hökhdgfsjh kjgh dh hdgöf h h ö ökhkjhgdöhg jdhf kj ök ökdfj ödfj dfjkj kjg kj kjdökgh ödh öhg   g  g   

   - no autofill after the second line
   - M-RET gives: setq: Symbol’s function definition is void:
     org-in-regexp



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?


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

This is not the case with bullet lists:

- o ushurgh dusrh gdrhf oudrhesurgh urhrh oughou hortus houtgsh
  ou houhort rtgshM-RET
- 


Could you give me a hint on how to debug this?


Thanks, Gregor

  parent reply	other threads:[~2018-05-06 10:43 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 [this message]
2018-05-06 11:32             ` Nicolas Goaziou
2018-05-07  9:13               ` Gregor Zattler
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=87bmdtkqtl.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).