<Regenaxer>
I find it fatal if it "saves" something in the wrong moment
<Regenaxer>
me too, all day
<Regenaxer>
But I save at very specific moments only
<Regenaxer>
want to revert often
<razzy>
i mean, i cannot save file, because of runaway VIP
<Regenaxer>
that's why the :bak command
<Regenaxer>
and :kab
<Regenaxer>
I do :w very often
<razzy>
I think i lost my wanted changes
<razzy>
I am used to emacs backing up everything :D
<Regenaxer>
ok
<Regenaxer>
For me this would be a horror
<Regenaxer>
*I* want to be in control
<razzy>
so, i will do :bak every insert.
<Regenaxer>
I have non-saved changes only for very few seconds
<Regenaxer>
I change something, think, and the :w or not
<Regenaxer>
undo perhaps
<Regenaxer>
:w or undo
<razzy>
i see. I am not sure if I want a change, untill I test it. I hate loosing hour of productive work. I have few of them.
<Regenaxer>
exactly
<Regenaxer>
But :w at the *right* moment is easy
<Regenaxer>
I never have the * at the bottom for more than one or two changes
<razzy>
I can only kill runaway VIP yes?
<Regenaxer>
runaway how?
<razzy>
ctrl+e runaway expression
<Regenaxer>
I see
<Regenaxer>
I do that seldom
<Regenaxer>
But in an application
<Regenaxer>
I always do 'gz' before testing complicated changes
<Regenaxer>
the : (v) to continue
<Regenaxer>
I think I never use ^E
<Regenaxer>
very seldom
<razzy>
gz? (v)?
<Regenaxer>
As it runs in the context of Vip
<Regenaxer>
not the application
<Regenaxer>
yes, gz 'yield's Vip
<Regenaxer>
back to REPL
<Regenaxer>
then (v) continues
<Regenaxer>
I once showed in PilCon
<Regenaxer>
Not only do I :w very often, but I almost always then do F2 to check the difference to the last :bak
<Regenaxer>
paranoid
<Regenaxer>
Either F2, or :$diff %- % for larger changes
<Regenaxer>
then, when I'm sure that I *want* the change, I do :bak
cranium has joined #picolisp
<beneroth>
keep in mind,that an autosave feature is a potential security risk - many people edit website files on live server and are then surprised when people can download their source code (usually the config file with DB credentials) as .bak or #file
<beneroth>
of course my argument is that files are public by default in webservers is a horrible design error, should be an explicit whitelist, but so are things.
<beneroth>
I'm also in the saving-every-few-keystrokes-population.. but I I make a habit of using the shortcut keys for this until it becomes muscle memory. I tend not to like auto-save feature of editors, because they produce so many files, easy to forget to clean up.
<beneroth>
I use git to restore a safe version if I'm unsure about a change. sometimes I do some extra commits just for that purpose.
<Regenaxer>
Hi beneroth! Interesting
<Regenaxer>
Also always interesting how everyone has different editing habits
<Regenaxer>
bbl now, tel meeting
schulze has joined #picolisp
<beneroth>
yeah, same :)
<razzy>
i will experiment with gz (v). I will propably do automated :bak with every third ESC. I agree about :bak security risks. Bak files could be easily search&deleted.
<Nistur>
mornin'
<beneroth>
morning Nistur
<Nistur>
o7
inara has joined #picolisp
memories_ has joined #picolisp
memories has quit [*.net *.split]
beneroth has quit [*.net *.split]
DKordic has quit [*.net *.split]
mario-goulart has quit [*.net *.split]
inara` has quit [*.net *.split]
schulze has quit [Ping timeout: 265 seconds]
schulze has joined #picolisp
mario-goulart has joined #picolisp
beneroth has joined #picolisp
<Regenaxer>
ret
cranium has quit [Quit: Leaving]
<beneroth>
Regenaxer, there is no function to check if a fd is still good (to write), correct?
<beneroth>
e.g. like (poll) when reading
<beneroth>
or could I use 'poll for this too?
<beneroth>
use case: piped process, might already be terminated (then I don't care), but if not I would like to send an exit command to it before (close)
<aw->
beneroth: hi
<beneroth>
aw-, hi :)
<aw->
if you know the pid of the process, you can do (kill *Process_pid 0)
<beneroth>
ah, perfect, exactly what I need
<beneroth>
many thansk aw- !
<beneroth>
thanks!
<aw->
np
<aw->
i have it in some of my code, where a child process checks if the parent process is dead (orphaned?) and if yes then it exits:
<beneroth>
I didn't not know about signal zero, very nice.