emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: newline or no newline at end of capture: expected behavior
Date: Wed, 23 Sep 2020 14:29:30 -0700	[thread overview]
Message-ID: <CAJcAo8uts1Zxgh59B9AN21gnvEZ3gP+wim25iSQ6qkiSgdGemQ@mail.gmail.com> (raw)
In-Reply-To: <87d02darcf.fsf@gnu.org>

i have been trying various hooks so this might not be the worst case,
but i know that finalizing a completely empty buffer will insert a
newline after the target.  that can't be worked around with hooks.


On 9/23/20, Bastien <bzg@gnu.org> wrote:
> Hi Samuel,
>
> Samuel Wales <samologist@gmail.com> writes:
>
>> basically i am getting unwanted newlines all over the place when i
>> capture.  but i want to confirm expected behavior for all 4 questions.
>
> Let's take this one by one.
>
> Can you provide the *worst* use case of Org going completely insane
> regarding empty lines after captured notes?
>
> --
>  Bastien
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html


  reply	other threads:[~2020-09-23 21:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20  5:29 newline or no newline at end of capture: expected behavior Samuel Wales
2020-09-20  5:36 ` Samuel Wales
2020-09-23  7:24   ` Bastien
2020-09-23 21:29     ` Samuel Wales [this message]
2020-09-23 21:30   ` Samuel Wales
2020-09-27  4:13     ` Samuel Wales
2020-09-27  7:16       ` Richard Lawrence
2020-09-27  7:42         ` Samuel Wales
2020-09-27 10:39           ` Nicolas Goaziou
2020-09-27 21:07             ` Samuel Wales
2020-09-27 21:08               ` Samuel Wales
2020-09-28  2:31                 ` Samuel Wales

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=CAJcAo8uts1Zxgh59B9AN21gnvEZ3gP+wim25iSQ6qkiSgdGemQ@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@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.
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).