From: Ulf Jasper <ulf.jasper@web.de>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 35645@debbugs.gnu.org
Subject: bug#35645: Fix icalendar--add-diary-entry/diary-make-entry interaction
Date: Mon, 13 May 2019 19:53:25 +0200 [thread overview]
Message-ID: <87mujqdywa.fsf@panama> (raw)
In-Reply-To: <m3d0kss3bl.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Wed, 08 May 2019 23:40:30 -0400")
Hi Thomas,
thanks for the patch(es)!
Am 08.05.2019 um 23:40 (-0400) schrieb Thomas Fitzsimmons:
> The attached patch, icalendar-diary-make-entry-fix-1.patch, adds
> omit-trailing-space and do-not-show parameters to diary-make-entry to
> allow it to operate more like a library function and less like an
> interactive function.
This patch (icalendar-diary-make-entry-fix-1.patch) looks good to me,
particulary from icalendar's point of view. Unit tests are not
affected.
> To keep the code mostly the same (so that I don't need to factor out
> another function), I've changed the original logic by adding a
> with-current-buffer wrapper, as shown in simplified form in
> diary-make-entry-with-current-buffer.patch. I'm hoping this keeps the
> default diary-make-entry logic exactly the same, but I'd like
> confirmation from someone more familiar with the subtleties of window
> and buffer manipulation.
The other patch file (diary-make-entry-with-current-buffer.patch) need
not be applied.
Maybe someone could confirm that the diary and the window/buffer things
are ok. I could then apply the patch.
next prev parent reply other threads:[~2019-05-13 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 3:40 bug#35645: Fix icalendar--add-diary-entry/diary-make-entry interaction Thomas Fitzsimmons
2019-05-13 17:53 ` Ulf Jasper [this message]
2019-05-14 0:13 ` Noam Postavsky
2019-05-24 2:49 ` Thomas Fitzsimmons
2019-06-03 18:30 ` Ulf Jasper
2019-06-07 9:21 ` Eli Zaretskii
2019-06-07 12:37 ` Thomas Fitzsimmons
2019-06-08 1:36 ` Thomas Fitzsimmons
2019-06-08 6:35 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mujqdywa.fsf@panama \
--to=ulf.jasper@web.de \
--cc=35645@debbugs.gnu.org \
--cc=fitzsim@fitzsim.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.