Hi,

Walter Dnes <waltdnes@???> writes:

> 1) My eyesight isn't what it used to be. How do I get a larger X cursor
> / mouse pointer?
>
> 2) On Gentoo, vim would return to the line where it had been when I left
> the previous edit session. In Devuan. vim always starts at the first
> line. Also, when editing a bash script, if a line is indented, hitting
> {RETURN} will result in the new line indented; not on Devuan. How do I
> get that back?

Not using vim myself but the manual page suggest you use

:help initialization

to see what you might want to put in ~/.vimrc to get this behaviour
back.

> 3) Speaking of bash scripts, I ran into something not-so-minor today,
> which prompted this message. Environmental variables ${LINES} and
> ${COLUMNS} exist at the commandline, but not in a bash script. Typing

LINES and COLUMNS are *shell* variables, not environment variables.
Hence they are not passed on to the process that runs the script.

> echo ${LINES} ${COLUMNS}
>
> ...at the commandline works, but the script
>
> #!/bin/bash
> echo ${LINES} ${COLUMNS}
>
> ...returns nothing. This happens in xterm and urxvt under X, and even
> in a textmode console outside of X. This kills a script of mine that
> USED TO WORK under Gentoo.

A quick search for COLUMNS in the `man bash` output suggests that you
may want to add

shopt checkwinsize

to your script

> I'm not here to slag Devuan. I'm merely asking how to add/restore
> certain functionality.

Hope this helps,
--
Olaf Meeuwissen