all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "pierre kobylanski" <pierre.kobylanski@gmail.com>
Cc: 424@debbugs.gnu.org
Subject: bug#424: new feature: killed-buffer
Date: Mon, 29 Feb 2016 15:56:21 +1100	[thread overview]
Message-ID: <874mcsxgga.fsf@gnus.org> (raw)
In-Reply-To: <5d706d390806160116k872a3e0o1d824a6748630d7d@mail.gmail.com> (pierre kobylanski's message of "Mon, 16 Jun 2008 10:16:19 +0200")

"pierre kobylanski" <pierre.kobylanski@gmail.com> writes:

> I'd like to propose a new feature for emacs: the capability to easily
> re-open previously killed buffers. Maybe someone else would appreciate
> it.
>
> It proposes three user functions:
>
>  * killed-buffers-mode
>      Activate/Deactivate remembering killed buffers. To avoid tricky
>      cases, only buffer associated with an existing file are taken
>      into account.
>
>  * restore-last-killed-buffer
>      Restore previously killed buffer. The number of
>      killed buffers to remember is configurable.
>      Ex: (global-set-key [(meta f8 )] 'restore-last-killed-buffer)

[...]

>  * require file-marker.el
>      This is a second file, that defines the file-marker structure.
>      Basically, it looks like a marker: it handles a filename and a
>      point. But I can't use markers as they end with buffer death.

This is perhaps covered by the desktop package (along with recentf) now?
I mean, especially the file marker stuff.  But perhaps desktop doesn't
keep track of killed buffers?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2016-02-29  4:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  8:16 bug#424: new feature: killed-buffer pierre kobylanski
2008-06-17 20:22 ` Stefan Monnier
2017-03-14  4:50   ` npostavs
2016-02-29  4:56 ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874mcsxgga.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=424@debbugs.gnu.org \
    --cc=pierre.kobylanski@gmail.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 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.