emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Either zero or two newlines with org-agenda-block-separator, cannot seem to get one?
Date: Thu, 09 Feb 2023 11:53:16 -0500	[thread overview]
Message-ID: <87edqy4w77.fsf@isnotmyreal.name> (raw)
In-Reply-To: <33fe6d20c0591fedbdd8c6ea78e34370@isnotmyreal.name>

Hello List,

I had sent original email to the list some time ago, never received a
reply.

Hopefully I have set the correct headers for proper threading; if not
the OP can be found at (either of) these URLs:

https://yhetil.org/orgmode/33fe6d20c0591fedbdd8c6ea78e34370@isnotmyreal.name/

https://list.orgmode.org/33fe6d20c0591fedbdd8c6ea78e34370@isnotmyreal.name/

I just looked at latest master(main) and It looks like this part of the
function `org-agenda-prepare' (in org-agenda.el) remains the same:

#+begin_src emacs-lisp
		(insert "\n"
			(if (stringp org-agenda-block-separator)
			    org-agenda-block-separator
			  (make-string (window-max-chars-per-line) org-agenda-block-separator))
			"\n"))
#+end_src

This results in problem mentioned in title.

I guess no one else is affected/bothered by this?

I have been patching it locally, it would be nice not to have to manage
that any longer.

-- 
Cheers,
TRS-80



  reply	other threads:[~2023-02-09 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 22:09 Either zero or two newlines with org-agenda-block-separator, cannot seem to get one? TRS-80
2023-02-09 16:53 ` TRS-80 [this message]
2023-02-10  8:25   ` Detlef Steuer

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=87edqy4w77.fsf@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --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).