emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@uva.nl>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: italics and fill paragraph behavior
Date: Fri, 18 Jul 2008 07:44:07 -0700	[thread overview]
Message-ID: <B2C81CBF-A65A-44AE-9B19-70C48CCD1FFB@uva.nl> (raw)
In-Reply-To: <f46c52560807180126n384e703ctcb7774e16435d7a6@mail.gmail.com>


On Jul 18, 2008, at 1:26 AM, Rustom Mody wrote:

> 1. When I ue italics with  /something in italics/ and the text spans
> across multile lines org arbitrarily does from italics into roman and
> back ( in a way which I cannot fathom).

By default Org looks only for a max of two lines for emphasis.  You  
can change this by customizing the variable org-emphasis-regexp- 
components, the last element gives the max number of lines you want to  
allow.  A restart of Emacs maybe required after you changed this  
before it becomes effective.

Also, generally font-lock can have problems with font lock expressions  
that span multiple lines while you type them.  For example, when you  
type

  /bkjkkjjk .... text including one newline .... lkjflkjsl/

font-lock fails to see this.  Do M-x font-lock-fontify-buffer to fix  
such cases.  Next time you open the buffer, font-lock does look at the  
entire buffer and finds such multiline locations.

> Is there some other prefered way for multiline italics?

You can use @<i> .... @</i> if you are only interested in italics for  
HTML export, but I do not think this is a "preferred" way.

> 2. M-q (fill-paragraph) messes up paragraphs which have lines ending
> in '\\' ie it joins lines ending \\ to the next and the \\ stops
> acting

Yes, this is a problem I do not know how to fix.

- Carsten

      reply	other threads:[~2008-07-18 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  8:26 italics and fill paragraph behavior Rustom Mody
2008-07-18 14:44 ` Carsten Dominik [this message]

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=B2C81CBF-A65A-44AE-9B19-70C48CCD1FFB@uva.nl \
    --to=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rustompmody@gmail.com \
    /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).