all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: pierre.kobylanski@gmail.com, 424@debbugs.gnu.org
Subject: bug#424: new feature: killed-buffer
Date: Tue, 14 Mar 2017 00:50:07 -0400	[thread overview]
Message-ID: <871su0798g.fsf@users.sourceforge.net> (raw)
In-Reply-To: <jwvskvblsmv.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Tue, 17 Jun 2008 16:22:42 -0400")

tags 424 wontfix
close 424
quit

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>  * 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.
>
> Why not use a bookmark?

bojohan+news@dd.chalmers.se (Johan "Bockgård)" writes:

> Stefan Monnier <monnier@iro.umontreal.ca> 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.
>>
>> Could this be integrated with recentf, maybe?
>
> Cf. iswitchb-use-virtual-buffers.

Lars Ingebrigtsen <larsi@gnus.org> writes:

> "pierre kobylanski" <pierre.kobylanski@gmail.com> writes:
>
>>  * 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?

Since the OP never responded to any of the comments on their patch, I'm
closing this.





  reply	other threads:[~2017-03-14  4:50 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 [this message]
2016-02-29  4:56 ` Lars Ingebrigtsen

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=871su0798g.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=424@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.