unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Alexandre Oberlin" <email_through@migo.info>
To: help-gnu-emacs@gnu.org
Subject: Re: Enriched mode: avoid removing my manual indents
Date: Mon, 27 May 2013 16:15:55 +0200	[thread overview]
Message-ID: <op.wxqxwtq9hcorn8@eucalyptus> (raw)
In-Reply-To: mailman.458.1369661162.22516.help-gnu-emacs@gnu.org

Thanks Drew for your reply. Maybe this behavior is not a bug but it is  
certainly confusing to me.

I can use C-x TAB "increase-left-margin" of course, but then it changes  
the indentation of the whole previous paragraph! Typing RET or explicitely  
calling open-line does not seem to create a paragraph boundary. In order  
to create a new paragraph with a new indentation, it seems that I must:
1. type a series of RET (to be able to navigate afterwards without typing  
RET);
2. go to the first line in this series;
3. indent as desired and type text;
4. go to the next line using down arrow (RET would fall back to the  
previous indentation);
5. type TAB to apply the same indentation as the previous line and type  
text.

Ain’t this a bit awkward ?


Alexandre


  On Mon, 27 May 2013 15:25:46 +0200, Drew Adams <drew.adams@oracle.com>  
wrote:

>> I just don’t get the rationale of it and why it is so hard to disable.  
>> All
>> I want from enriched mode is persistent colors/bold/italic, otherwise  
>> the
>> standard indentation behavior of fundamental-mode and text-mode is OK  
>> for
>> me. I tried indent-to-column, use-hard-newlines and indented-text-mode
>> with no avail. Maybe I should try org-mode but I don’t have so much time
>> to learn such things.
>> >
>> > I use enriched mode extensively but if I start a new line say on  
>> column
>> > 8, then why does enriched mode think that is an error and put it back  
>> to
>> > beginning of line as soon as I type return ?
>
> You can use `M-x report-emacs-bug' to submit an enhancement request.  If  
> enriched mode couples indenting text with coloring it, and the two  
> cannot be dissociated, that sounds like something that could be improved.
>
> It's best to give a complete and simple recipe to repro the problematic  
> behavior, starting from `emacs -Q'.
>


-- 
Alexandre Oberlin
http://www.migo.info


  parent reply	other threads:[~2013-05-27 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 12:42 Enriched mode: avoid removing my manual indents Alexandre Oberlin
2013-05-27 12:59 ` Alexandre Oberlin
2013-05-27 13:25   ` Drew Adams
     [not found]   ` <mailman.458.1369661162.22516.help-gnu-emacs@gnu.org>
2013-05-27 14:15     ` Alexandre Oberlin [this message]
2013-05-27 18:55       ` Stefan Monnier
     [not found]       ` <mailman.475.1369680957.22516.help-gnu-emacs@gnu.org>
2013-05-28 11:50         ` Alexandre Oberlin
2013-06-04 11:52         ` Alexandre Oberlin
2014-02-15 17:30         ` [SOLVED] " Alexandre Oberlin
2014-02-15 17:30         ` Alexandre Oberlin
2014-02-15 17:32         ` Alexandre Oberlin

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.wxqxwtq9hcorn8@eucalyptus \
    --to=email_through@migo.info \
    --cc=help-gnu-emacs@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.
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).