From: Nicolas Goaziou <firstname.lastname@example.org> To: Samuel Wales <email@example.com> Cc: firstname.lastname@example.org, Richard Lawrence <email@example.com> Subject: Re: newline or no newline at end of capture: expected behavior Date: Sun, 27 Sep 2020 12:39:26 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAJcAo8t1MWi60CZU8SK0miQo8UogdsKg2ZLv6K6T=ubFCWjfBQ@mail.gmail.com> (Samuel Wales's message of "Sun, 27 Sep 2020 00:42:00 -0700") Hello, Samuel Wales <email@example.com> writes: > thank you. when i can, i will try explicitly setting all three to 0 > to see if that prevents the unwanted newlines, in the buffer with > newline on last line, and empty buffer, cases. > > the docstring says empty-lines defaults to 0, which is what i want. > it does not say what the default for after and before are. > > it /sounds/ like capture is supposed to produce the desired number > [and position] of empty lines regardless of whether the buffer is > empty or there is or is not a trailing newline on the final line of > hte buffer. is this more or less correct? I didn't read the whole thread, but a final newline is mandatory in all capture templates, independently on the number of desired blank lines. If such final newline is not provided, the capture mechanism will add one. The only exception is about empty capture templates, which are left as-is, i.e. a "final newline" is not added in that case. I don't know if that answers your question, but HTH. Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2020-09-27 10:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-20 5:29 Samuel Wales 2020-09-20 5:36 ` Samuel Wales 2020-09-23 7:24 ` Bastien 2020-09-23 21:29 ` Samuel Wales 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: newline or no newline at end of capture: expected behavior' \ /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
Code repositories for project(s) associated with this 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).