emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug in structmode++?
Date: Tue, 07 May 2013 14:28:23 +0200	[thread overview]
Message-ID: <86y5brug7s.fsf@somewhere.org> (raw)
In-Reply-To: 87ip2v83j3.fsf@bzg.ath.cx

Bastien wrote:
> Christopher Schmidt <christopher-TsugTnnrXQtNhJN0HIYqWA@public.gmane.org> writes:
>> Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>> Igor Sosa Mayor <joseleopoldo1792-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>
>>>> Thanks Nicolas. At least, I dont feel alone anymore... Is there any
>>>> chance this getting fixed somehow? I used to use it very often in my
>>>> emails and I miss it.
>>>
>>> I miss it, too.
>>>
>>> I didn't follow recent changes to orgstruct-mode, so I cannot help
>>> here.  I hope that someone more knowledgeable than I am will jump in.
>>
>> orgstruct(++)-mode used to set auto-fill-function to
>> 'org-auto-fill-function.  This behaviour is too intrusive so we removed
>> it.  You either need to indent secondary lines by hand or set
>> auto-fill-function back to org-auto-fill-function.
>
> I don't remember why it was too intrusive, it worked fine for me.
>
>> orgstruct++'s hijacker of org-insert-heading-respect-content did not
>> respect item bodies.  I fixed this in master a few minutes ago.
>
> I just tried with orgstruct-mode and I still have the problem.
>
> With orgstruct++-mode, M-RET on the second line of an item inserts an
> item correctly, but there is another problem (also for orgstruct-mode):
> M-RET on the first line of a two-lines item will insert the new item in
> the middle of the item...
>
> Thanks for taking care of this!

I also have the problems that, when writing itemized lists in emails, the
minor mode takes the "- " as a line prefix, and does repeat it over each line,
something such as:

- this is a long, long, long, long, long, long, long, long, long, really long,
- very long item.
^
^ This one has been inserted automatically, unlike the behavior we had before.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-05-07 12:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 15:03 Bug in structmode++? Igor Sosa Mayor
2013-05-02  8:31 ` Igor Sosa Mayor
2013-05-02  8:33   ` Nicolas Goaziou
2013-05-02  8:51     ` Igor Sosa Mayor
2013-05-02 13:37       ` Nicolas Goaziou
2013-05-06 17:07         ` Christopher Schmidt
2013-05-07 10:16           ` Bastien
2013-05-07 12:28             ` Sebastien Vauban [this message]
2013-05-07 14:31             ` Christopher Schmidt
2013-05-14  8:59               ` Bastien
2013-05-14 11:16                 ` Daniel Bausch
2013-05-12 14:10   ` The Dude
2013-05-12 14:59     ` Christopher Schmidt
2013-05-12 18:34       ` Igor Sosa Mayor
2013-05-23  6:29         ` The Dude

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=86y5brug7s.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).