From: Colin Baxter <m43cap@yandex.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: , help-gnu-emacs@gnu.org
Subject: Re: Diary comments
Date: Wed, 24 Feb 2021 06:01:45 +0000 [thread overview]
Message-ID: <878s7ec8c6.fsf@yandex.com> (raw)
In-Reply-To: <87r1l61a8d.fsf@web.de> (Michael Heerdegen's message of "Wed, 24 Feb 2021 03:16:18 +0100")
>>>>> Michael Heerdegen <michael_heerdegen@web.de> writes:
> Colin Baxter <m43cap@yandex.com> writes:
>> I am thinking of setting diary comments as
>>
>> #+begin_src elisp (setq diary-comment-start "<--") ;; No block
>> comments; one line only. (setq diary-comment-end "-->")
>> #+end_src
>>
>> These seem to be non-invasive settings, but I'm not certain. Has
>> anyone experienced issues with diary comments?
> I didn't ever use diary comments, but if you try and find
> problems, please don't hesitate to report them.
Ok, will do. I have several included diary files, which, if I don't
comment them, I will forget their details.
Best wishes,
prev parent reply other threads:[~2021-02-24 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:40 Diary comments Colin Baxter
2021-02-24 2:16 ` Michael Heerdegen
2021-02-24 6:01 ` Colin Baxter [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878s7ec8c6.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).