Re: how to force auto-save of buffers not visiting files, right now?

[Michael Heerdegen]

hw <hw@adminart.net> writes:

> When you use perltidy only right before you want to run and test your
> program, you still want to have a backup from before you used perltidy
> so that, if you need to, can try the version that wasn't altered by
> perltidy to see if that makes a difference.  Of course you can save
> backups manually, but it's nicer to have that automated.

But why isn't your code located in a buffer visiting a file?

> I can't possibly list all things that can go wrong.  Maybe you have never
> experienced that a computer or software doesn't work as it should or that
> things can go wrong.  If you want to find out, you might use wayland with
> sway [...]

X crashes often enough, sometimes including the kernel.  That's good
enough for me.

> Why would you expect that perltidy will never ever damage your source code
> so that you do not need to keep a copy of what you used it on?  That would
> be unreasonable.

That's what I don't understand: if it's your source code, why is your
question about "how to force auto-save of buffers not visiting files,
right now?"?

Michael.