From: Nick Dokos <email@example.com>
To: Richard Stanton <firstname.lastname@example.org>
Cc: email@example.com, "firstname.lastname@example.org" <email@example.com>
Subject: Re: How to reduce width of section separators in agenda view?
Date: Thu, 08 Mar 2012 13:30:12 -0500 [thread overview]
Message-ID: <5883.1331231412@alphaville> (raw)
In-Reply-To: Message from Richard Stanton <firstname.lastname@example.org> of "Thu\, 08 Mar 2012 10\:12\:34 PST." <40C7B1BFC291ED4E9D10436D07736A334700FA8B0D@EXMAIL7.haas.uc.berkeley.edu>
Richard Stanton <email@example.com> wrote:
> I have an agenda view set up as an org-agenda-custom-command,
> ("H" "Office and Home Lists"
> (tags-todo "OFFICE")
> (tags-todo "HOME")
> (tags-todo "COMPUTER")))
> This works fine, but I notice that each section of the agenda view is separated by a line of “=” signs 132 characters long, and when I print in portrait mode, these wrap onto the next line. How can I shorten these lines to only 80 characters wide?
> Thanks for any suggestions.
Check out the variable org-agenda-block-separator. C-h v org-agenda-block-separator RET says:
| org-agenda-block-separator is a variable defined in `org-agenda.el'.
| Its value is 61
| The separator between blocks in the agenda.
| If this is a string, it will be used as the separator, with a newline added.
| If it is a character, it will be repeated to fill the window width.
| If nil the separator is disabled. In `org-agenda-custom-commands' this
| addresses the separator between the current and the previous block.
| You can customize this variable.
(61 is '=')
So you can customize it and set it to a string of your choice, or you
can display the block agenda in a window of width <= 80 chars and then
print the window. Both suggestions untested but I hope one or the other
or both work.
next prev parent reply other threads:[~2012-03-08 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 18:12 How to reduce width of section separators in agenda view? Richard Stanton
2012-03-08 18:30 ` Nick Dokos [this message]
2012-03-08 21:57 ` Bernt Hansen
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).