From: TRS-80 <firstname.lastname@example.org>
Subject: Re: Using org-agenda-time-grid with lists
Date: Fri, 11 Dec 2020 12:23:28 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On 2020-12-11 11:48, firstname.lastname@example.org wrote:
> TRS-80 wrote:
>> On 2020-12-11 10:45, email@example.com wrote:
>> > Incidentally, how can one print a list in messages buffer?
>> Do you mean something other than standard:
> Correct, something other than "%s".
>> (message "%s" my-list)
>> I wrote some quite involved function to take a list of variables and
>> print them to Messages buffer, formatting them nicely. I use it when
>> debugging and writing code. However I am not sure that is what you
>> looking for or not?
> What is the biggest problem with printing lists that you have
I don't have any problem printing simple list. Well, maybe one case.
If the list is too long (because you only get some part of it in
Messages buffer). In that case, I do my function in fundamental-mode
with C-j (I think?) which put the results in the same buffer. Then you
can do <TAB> (or maybe it's <RET>?) and that will expand to the full
result, if you need to look at that.
But the reason I wrote my function was because I wanted to provide short
list of (separate) variables and have them print out to nicely formatted
message as intermediate structure code and/or for debugging purposes.
Which is nothing to do with lists, per say.
> Cheers always sounds better on a friday. :)
You make me thirsty all of a sudden! :)
next prev parent reply other threads:[~2020-12-11 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 14:59 Using org-agenda-time-grid with lists steve-humphreys
2020-12-11 15:28 ` Marco Wahl
2020-12-11 15:45 ` steve-humphreys
2020-12-11 16:39 ` TRS-80
2020-12-11 16:48 ` steve-humphreys
2020-12-11 17:23 ` TRS-80 [this message]
2020-12-11 18:18 ` Christopher Dimech
2020-12-11 18:38 ` TRS-80
2020-12-11 22:22 ` Marco Wahl
2020-12-11 23:04 ` steve-humphreys
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).