From: Noorul Islam <noorul@noorul.com>
To: Marcel van der Boom <marcel@hsdev.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: org-capture adds newline(s) when it should not
Date: Tue, 26 Oct 2010 14:09:48 +0530 [thread overview]
Message-ID: <AANLkTimjiYEgW5T7A3m+0tEz1v-yPs4R9DNjNXNEUFaq@mail.gmail.com> (raw)
In-Reply-To: <20101026103557.3ae4ae1c@hsdev.com>
On Tue, Oct 26, 2010 at 2:05 PM, Marcel van der Boom <marcel@hsdev.com> wrote:
> On di 26-okt-2010 13:54
> Noorul Islam <noorul@noorul.com> wrote:
>
>>On Tue, Oct 26, 2010 at 1:46 PM, Marcel van der Boom
>><marcel@hsdev.com> wrote:
>>> On di 26-okt-2010 06:35
>>> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>>
>>>>>> I find that puzzling. What might have changed in Emacs 24 to
>>>>>> cause such
>>>>>> differences? I do not use Emacs 24 on a day-to-day basis yet.
>>>>>>
>>>>>
>>>>> On emacs 24 (newline 0) inserts a new line which I think is
>>>>> incorrect.
>>>>
>>>>Sounds like a but to me too.
>>>>For now I am working around this in the latest git version.
>>>>
>>>>Marcel, this should be fixed. Could you please submit a bug report
>>>>to Emacs 24, stating that (newline 0) does insert a newline?
>>>
>>> The newlines are indeed fixed, but I have to manually widen the
>>> target buffer before the captured entry is visible.
>>>
>>> Tried this on emacs 23 as well and there it is functioning properly,
>>> so this seems emacs 24 specific too.
>>
>>How did you fix it?
>>
> Sorry, I wasn't clear. Capturing with emacs 23 with the latest git
> version works perfectly.
>
> If I use emacs 24 with the latest git capturing works with respect to
> the newlines, but leaves the captured entry invisible in the target
> buffer until I widen the buffer.
>
I thought it got automatically fixed. But I could see this.
commit 2a58795e1958210b96e9adee52b9dd68f7d1f50e
Author: Carsten Dominik <carsten.dominik@gmail.com>
Date: Tue Oct 26 06:34:16 2010 +0200
Fix empty line bug in capture
* lisp/org-capture.el (org-capture-empty-lines-before):
(org-capture-empty-lines-after): Make sure the n=0 does not insert any
newlines.
Thanks and Regards
Noorul
prev parent reply other threads:[~2010-10-26 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 10:51 org-capture adds newline(s) when it should not Marcel van der Boom
2010-10-25 11:18 ` Noorul Islam
2010-10-25 11:58 ` Noorul Islam
2010-10-25 12:16 ` Carsten Dominik
2010-10-26 4:29 ` Noorul Islam
2010-10-26 4:35 ` Carsten Dominik
2010-10-26 5:04 ` Noorul Islam
2010-10-26 5:36 ` Noorul Islam
2010-10-26 7:38 ` Marcel van der Boom
2010-10-26 8:16 ` Marcel van der Boom
2010-10-26 8:24 ` Noorul Islam
2010-10-26 8:35 ` Marcel van der Boom
2010-10-26 8:39 ` Noorul Islam [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=AANLkTimjiYEgW5T7A3m+0tEz1v-yPs4R9DNjNXNEUFaq@mail.gmail.com \
--to=noorul@noorul.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=marcel@hsdev.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).