From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Cursive and 3 lines Date: Mon, 27 Jan 2014 11:50:59 +0100 Message-ID: <87y521u298.fsf@bzg.ath.cx> References: <20140127102127.GA20080@pedroche.uni-erfurt.de> <87iot5en73.fsf@bzg.ath.cx> <20140127103451.GA22749@pedroche.uni-erfurt.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51167) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7jmZ-0001oe-AB for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:51:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7jmQ-0004XN-RQ for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:51:11 -0500 Received: from mail-we0-x233.google.com ([2a00:1450:400c:c03::233]:36053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7jmQ-0004XE-L7 for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:51:02 -0500 Received: by mail-we0-f179.google.com with SMTP id w62so4997904wes.38 for ; Mon, 27 Jan 2014 02:51:01 -0800 (PST) In-Reply-To: <20140127103451.GA22749@pedroche.uni-erfurt.de> (Igor Sosa Mayor's message of "Mon, 27 Jan 2014 11:34:52 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Igor Sosa Mayor Cc: emacs-orgmode@gnu.org Hi Igor, Igor Sosa Mayor writes: > Am Mon, Jan 27, 2014 at 11:25:20AM +0100, Bastien wrote: >> You need to customize `org-emphasis-regexp-components', the last >> element of this option defines the number of newlines to accept. > > thanks for your answer. Unfortunately it is not really working. I have > at the moment > (setq org-emphasis-regexp-components > '(" \t('\"{" "- \t.,:!?;'\")}\\" " \t\r\n,\"'" "." 3)) Caveat: you need to restart Emacs for a change in this option to take effect (see the docstring of the option.) > but I get the saem result (emacs version: 24.3)... maybe it is > conflicting with other configurations (I have a very very long > org-config...) Yes, providing a minimal configuration file to reproduce the problem usually helps getting rid of the problem :) -- Bastien