public inbox for howm-eng@lists.osdn.me
 help / color / mirror / Atom feed
From: khi at users.sourceforge.jp (khi at users.sourceforge.jp)
Subject: [Howm-eng 57] Re: C-c C-c: save and kill buffer ?
Date: Wed, 09 Apr 2008 22:22:22 +0900	[thread overview]
Message-ID: <m3prszjh81.wl@id.domain> (raw)
In-Reply-To: <200804090000.m39009F1004703@localhost.localdomain>

At Wed, 9 Apr 2008 02:00:09 +0200,
Xavier Maillard wrote:
> ;; From elscreen-howm
> (defun howm-save-and-kill-buffer ()

> Why not put this in the howm code ?

I agree that these features are convenient for many users.
* C-c C-c saves and kills the current buffer.
* If we save an empty buffer, its corresponding file is removed.
But, their benefit is not limited to howm.
I recommend you to define them *globally*.

-- 
khi at users.sourceforge.jp



  reply	other threads:[~2008-04-09 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  6:29 [Howm-eng 50] " xma
2008-04-08 15:57 ` [Howm-eng 51] " khi
2008-04-09  0:00   ` [Howm-eng 52] " xma
2008-04-09 13:22     ` khi [this message]
2008-04-12  0:00       ` [Howm-eng 65] " xma

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=m3prszjh81.wl@id.domain \
    --to=howm-eng@lists.osdn.me \
    /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).