Tip for Desktop Memory management, new vm tuning option

[Liam Proven]

On Tue, 30 Jul 2019 at 18:33, Ralf Mardorf via ubuntu-users
<ubuntu-users at lists.ubuntu.com> wrote:
>
> The word 'simple' in combination with 'vi*' or 'emacs' just for editing
> a value is grotesk. 'vi*' or 'emacs' for sure have got advantages for
> some purposes, but for editing a value I can't imagine something more
> complicated than using one of those editors.

*Chuckle* I know exactly what you mean, but do bear in mind that Bret
is, ah, "of a certain age" -- he has been around at bit. When I saw my
first Unix box in 1988 (SCO Xenix), Vi was the only interactive editor
available.

(Edlin was the only built-in editor on PC/MS-DOS back then. Vi is at
least better than Edlin.)

So although I hate it, I know it and can use it for simple stuff.

> IMO the right tools are
> 'echo', 'printf', 'sed'

Diaagree. Too complex.

> or easy to use editors such as 'nano'

Agreed. Or Pico or Joe.

> or even a
> GUI editor such as 'xed',

Agreed, but brings in extra issues when editing files owned by root.
E.g. on openSUSE I cannot run graphical tools from sudo/su *at all*.
It is intentionally blocked. It's easy to circumvent on *buntu or
Debian if using X.org but less so with Wayland and not at all on
openSUSE.

So I do not advise it.

I do recommend this:
https://os.ghalkes.nl/tilde/

I put it on all my machines. Absolutely my favourite console editor
for Linux, but still has issues and rarely installed as standard.

> unless a user for some other reasons does use
> 'vi*' or 'emacs' on a daily basis.

I think this is the case in this instance.

-- 
Liam Proven - Profile: https://about.me/liamproven
Email: lproven at cix.co.uk - Google Mail/Hangouts/Plus: lproven at gmail.com
Twitter/Facebook/Flickr: lproven - Skype/LinkedIn: liamproven
UK: +44 7939-087884 - ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053