[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#424: new feature: killed-buffer
From: |
npostavs |
Subject: |
bug#424: new feature: killed-buffer |
Date: |
Tue, 14 Mar 2017 00:50:07 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
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.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#424: new feature: killed-buffer,
npostavs <=