From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme Configuration
Date: Fri, 7 Aug 2009 18:54:42 +0200 [thread overview]
Message-ID: <56a297000908070954q368a6c5cu3e6f239261c437d4@mail.gmail.com> (raw)
In-Reply-To: <df49a7370908070842k734c4c0aib88cef484bb8e236@mail.gmail.com>
you mean outside of the dump when acme is dies for reasons other than
being killed/exited?
with win state, how are you going to handle the state of the shell? I
can see why they're dynamic, it could be potentially misleading to see
a changed namespace/rfork etc... and expect the shell to have the same
environment as the history.
I definitely like your restored from ideas.
I wouldn't worry about getting the patch accepted or not. Just go for it.
On Fri, Aug 7, 2009 at 5:42 PM, roger peppe<rogpeppe@gmail.com> wrote:
> the Include path.
> contents of win buffers.
> Undo/Redo history.
>
> ok, the last might be pushing it a bit,
> but ideally i'd like to be able to dump
> an acme session and restore it without
> any loss of continuity, and the Undo/Redo history
> is a very useful part of my acme context.
>
> while i'm about it, there are a few other dump
> features i'd like to see:
> - automatic dumping every 30s or so in case of a crash.
> - Dump would dump to the restored-from file rather than
> $home/acme.dump by default.
> - atomic dump file creation - if, for some reason,
> acme dies half-way through dumping, i don't
> want the old dump file to be erased with a dud
> new one.
>
> most of this should be fairly straightforward,
> i've just not made space in my life to do it yet.
>
> and i doubt it would be accepted as a patch anyway.
>
>
> 2009/8/7 Noah Evans <noah.evans@gmail.com>:
>> What other stuff are you thinking of?
>>
>> On Fri, Aug 7, 2009 at 4:02 PM, roger peppe<rogpeppe@gmail.com> wrote:
>>> 2009/8/7 Noah Evans <noah.evans@gmail.com>:
>>>> The dump doesn't preserve indent state
>>>
>>> personally, i think it should.
>>>
>>> and some other stuff as well.
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2009-08-07 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 8:37 Aaron W. Hsu
2009-08-07 9:20 ` Daniel Lyons
2009-08-07 9:39 ` erik quanstrom
2009-08-07 13:34 ` Jason Catena
2009-08-07 13:50 ` Noah Evans
2009-08-07 14:02 ` roger peppe
2009-08-07 14:28 ` Noah Evans
2009-08-07 15:42 ` roger peppe
2009-08-07 15:48 ` erik quanstrom
2009-08-07 16:05 ` ron minnich
2009-08-07 16:54 ` Noah Evans [this message]
2009-08-07 17:07 ` Iruata Souza
2009-08-07 17:16 ` erik quanstrom
2009-08-07 17:23 ` yy
2009-08-07 18:50 ` Jason Catena
2009-08-07 19:00 ` yy
2009-08-08 4:16 ` 6o205zd02
2009-08-07 20:07 ` Uriel
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=56a297000908070954q368a6c5cu3e6f239261c437d4@mail.gmail.com \
--to=noah.evans@gmail.com \
--cc=9fans@9fans.net \
/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).