Le 06/02/2018 à 00:17, Steve Litt a écrit :
Oh Oh. Here's what my Chromium browser says the last paragraph of the
document says:
=======================================================
Sakura is much more featureful than discussed in this document, and its
features are easy to use. Perform command sakura --help for more
details, peruse the ~/.config/sakura/secura.conf file for even more,
and for the utmost info on this program's behavior, look at its source
code.
=======================================================
My intent was to precede the leading slash with a tilde. I must have
done something that renders wrong on some browsers. I tested with my
handy dandy XML checker and the doc is well formed XML, which*usually*
means it will play right with most browsers, but...
On what browser did you observe the lack of the tilde?
My remark was about "secura.conf" instead of "sakura.conf"
What the difference between hitting <ctrl><shift>T and hitting
<tab> ?
Ctrl+Shift+t adds a tab on top. Hitting the tab key queries the files
in the directory and asks you to select (this is a function of
bash/dash, not the terminal emulator).
Stupid me!
<personal-opinion>Sakura rewriting its config file on exit is
definitely a bad feature.</personal-opinion>
I'd rather have two files: One for config, the other for persistent
state. I'd prefer the former not be overwritten, and the latter
overwritten and headed by a comment not to edit it directly.
This could be done by wrapping the invocation into a script. Yet
it's not satisfactory. Actually I don't see the need for recording the
state of a terminal emulator (which state, btw?).
In general I like applications (and desktop session) to start from
fresh instead of restoring the dirt accumulated in the previous
invocations. In some cases, restoring the state can lead you to
restarting always in a broken state you cannot go out of.
Didier
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
