From: Pieter Praet <pieter@praet.org>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Library of Babel source block
Date: Sun, 28 Aug 2011 20:20:29 +0200 [thread overview]
Message-ID: <87r545qtxu.fsf@praet.org> (raw)
In-Reply-To: <m1ipphihpz.fsf_-_@tsdye.com>
On Sun, 28 Aug 2011 07:11:36 -1000, tsd@tsdye.com (Thomas S. Dye) wrote:
> [...]
> I tried to follow Bastien's suggestion about adding a change log to the
> commit message, but ended up with something that looks different than
> his example. I'm not sure why--perhaps Bastien is not working in magit,
> so his instructions apply to some other context?
> [...]
Bastien was referring to `add-change-log-entry{,-other-window}', which is
part of Emacs [1], and is mainly intended to add entries to a dedicated
ChangeLog file (when this file isn't present, it'll open a new buffer
for the entry). While it *does* most definitely produce properly formatted
entries when called with point on a diff hunk, it always requires the extra
step of yanking the entry into your commit message buffer.
When using Magit (which I highly recommend) however, you can add properly
formatted entries *much* faster by positioning point on a (staged) diff
hunk in the status buffer, and calling `magit-add-log' (bound to 'C') [2].
If you don't already have a commit buffer ('*magit-edit-log*'), it will
create one for you, so you don't even need to call `magit-log-edit'
(bound to 'c') in advance anymore. :)
Peace
--
Pieter
[1] [[info:emacs#Change Log]]
[2] [[info:magit#Staging and Committing]]
next prev parent reply other threads:[~2011-08-28 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 18:33 Library of Babel function Thomas S. Dye
2011-08-28 14:44 ` Eric Schulte
2011-08-28 17:11 ` [PATCH] Library of Babel source block Thomas S. Dye
2011-08-28 18:16 ` Eric Schulte
2011-08-28 18:20 ` Pieter Praet [this message]
2011-08-28 19:03 ` Thomas S. Dye
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=87r545qtxu.fsf@praet.org \
--to=pieter@praet.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).