From: Karl Chen <quarl@NOSPAM.quarl.org>
Subject: hashcash - buffer modification
Date: Tue, 14 Nov 2006 15:48:03 -0800 [thread overview]
Message-ID: <quack.20061114T1548.lthmz6tmvyk@roar.cs.berkeley.edu> (raw)
Hi, I'm glad hashcash is now integrated and on by default.
One thing that bothers me about the asynchronous payment
insertion, which is otherwise awesome, is that it sets the message
buffer modification bit.
I use the advice below to get around it; how about integrating it
into hashcash-insert-payment-async-2?
(defadvice hashcash-insert-payment-async-2 (around kc-hashcash-set-notmodified
(buffer &rest l)
activate)
(let ((modified (buffer-modified-p buffer)))
ad-do-it
(save-excursion
(set-buffer buffer)
(set-buffer-modified-p modified))))
--
Karl 2006-11-14 15:44
next reply other threads:[~2006-11-14 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 23:48 Karl Chen [this message]
2006-11-15 5:00 ` Katsumi Yamaoka
2006-11-15 8:37 ` Karl Chen
2006-11-15 14:22 ` gdt
2006-11-16 2:16 ` Katsumi Yamaoka
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=quack.20061114T1548.lthmz6tmvyk@roar.cs.berkeley.edu \
--to=quarl@nospam.quarl.org \
--cc=quarl+dated+1163979873.4d5c88@nospam.quarl.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.
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 NNTP newsgroup(s).