emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Girard <nicolas.girard@nerim.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: [PATCH] Suppress extra newlines around source code in LaTeX export
Date: Mon, 14 Dec 2009 16:41:41 +0100	[thread overview]
Message-ID: <66D2118D-3D77-4034-AE7A-300CFB66CF48@gmail.com> (raw)
In-Reply-To: <51b0095d0912101337w3b741b71ke0498a78e1e51f63@mail.gmail.com>

Actually,  I cannot reproduce this problem - I do not see the extra  
newline.

- Carsten

On Dec 10, 2009, at 10:37 PM, Nicolas Girard wrote:

> 2009/12/9 Nicolas Girard <nicolas.girard@nerim.net>:
>> 2009/12/9 Carsten Dominik <carsten.dominik@gmail.com>:
>>
>>>> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
>>>> index 4c4d540..75ee548 100644
>>>> --- a/lisp/org-exp.el
>>>> +++ b/lisp/org-exp.el
>>>> @@ -2423,7 +2423,7 @@ INDENT was the original indentation of the  
>>>> block."
>>>>                             (concat (car org-export-latex- 
>>>> verbatim-wrap)
>>>>                                     rtn (cdr
>>>> org-export-latex-verbatim-wrap)))
>>>>                          '(org-protected t))
>>>> -                     "#+END_LaTeX\n"))
>>>> +                     "#+END_LaTeX"))
>>>>             ((eq backend 'ascii)
>>>>              ;; This is not HTML or LaTeX, so just make it an  
>>>> example.
>>>>              (setq rtn (org-export-number-lines rtn 'ascii 0 0  
>>>> num cont
>>>> rpllbl fmt))
>>>
>>>
>>> I have fixed this part, in a different way though.
>>>
>>
>> I'm afraid there are still extra paragraphs resulting from an extra
>> newline after code blocs.
>>
>> Consider the following test chunk:
>>
>> #=====
>> This is a new paragraph
>> #+begin_src emacs-lisp
>> (setq ispell-program-name "aspell")
>> #+end_src
>> continuing after the code bloc.
>> #=====
>>
>> Using the freshest code, is is translated to
>>
>> %=====
>> This is a new paragraph
>> \lstset{language=Lisp}
>> \begin{lstlisting}
>> (setq ispell-program-name "aspell")
>> \end{lstlisting}
>>
>> continuing after the code bloc.
>> %=====
>>
>>
>
>
> Unfortunately this problem remains: processing
>
> #=====
> This is a new paragraph
> #+begin_src emacs-lisp
> (setq ispell-program-name "aspell")
> #+end_src
> continuing after the code bloc.
> #=====
>
> still inserts an extra newline just before "continuing (...)".
>
> Cheers,
>
> -- 
> Nicolas
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

  reply	other threads:[~2009-12-14 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 21:03 [PATCH] Suppress extra newlines around source code in LaTeX export Nicolas Girard
2009-12-03 14:42 ` Carsten Dominik
2009-12-05 11:58 ` Nicolas Girard
2009-12-09 10:00   ` Carsten Dominik
2009-12-09 22:21     ` Nicolas Girard
2009-12-10 21:37       ` Nicolas Girard
2009-12-14 15:41         ` Carsten Dominik [this message]
2009-12-15 10:55           ` Nicolas Girard
2009-12-16 10:48             ` Carsten Dominik
2009-12-09 22:50     ` Nicolas Girard
2009-12-09 23:56       ` Nicolas Girard
2009-12-10  8:08         ` Carsten Dominik
2009-12-10 21:38           ` Nicolas Girard
2009-12-10  8:08       ` Carsten Dominik
2009-12-10 21:39         ` Nicolas Girard

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=66D2118D-3D77-4034-AE7A-300CFB66CF48@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicolas.girard@nerim.net \
    /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).