Hardware cursor and console colours resetting when starting mutt

[David Woodfall]

On Sunday 30 September 2018 05:32,
Dave Woodfall <dave at dawoodfall.net> put forth the proposition:
> On Saturday 29 September 2018 23:33,
> Dave Woodfall <dave at dawoodfall.net> put forth the proposition:
> > On Sunday 30 September 2018 08:17,
> > Cameron Simpson <cs at cskk.id.au> put forth the proposition:
> > > On 28Sep2018 23:06, David Woodfall <dave at dawoodfall.net> wrote:
> > > > On Friday 28 September 2018 17:44,
> > > > Patrick Shanahan <paka at opensuse.org> put forth the proposition:
> > > > > * David Woodfall <dave at dawoodfall.net> [09-28-18 17:37]:
> > > > > > In the (framebuffer) console I've used the standard escape codes to
> > > > > > set a small 1/3 block cursor to make it more visible, and softened
> > > > > > the colours to not be so stark.  They were a bit of a headache
> > > > > > before, and the normal cursor is very hard to see.
> > > > > >
> > > > > > Unfortunately, when I start mutt everything resets back to the
> > > > > > defaults.  I only see a couple of settings regarding the cursor, but
> > > > > > they don't seem to help.  I've tried running with a -F /dev/null so
> > > > > > it doesn't seem to be something in my config.  Is there any way of
> > > > > > avoiding this?
> > > > > >
> > > > > > In screen it's not so bad, but the cursor resets even just switching
> > > > > > to the window where mutt is running.  The colours remain as they were
> > > > > > though.
> > > > > >
> > > > > > The cursor code I use is:
> > > > > >
> > > > > > printf '\e[?3c'
> > > > > >
> > > > > > Any ideas?
> > > > >
> > > > > your chosen terminal is undoubted the cause.  I run a tmux session on my
> > > > > server and attach to it remotely usually via yakuake(konsole) but have not
> > > > > made any effort to change the cursor.
> > > > >
> > > > > you have pretty well removed mutt from the equasion using "-F /dev/null".
> > > >
> > > > I'm using the vanilla linux console (i.e. no X and 16 colours) plus screen.
> > > > Don't really have a lot of choice.
> > >
> > > Does the behaviour persist if you don't use screen? I'm wondering if screen's terminal management is
> > > reseting your cursor change.
> > >
> > > Conversely, does the behaviour occur if you use screen but don't use mutt (but _do_ use some other curses
> > > programme like vim inside screen)?
> > >
> > > Just trying to isolate where the reset is coming from. And I don't have a convenient linux framebuffer
> > > console to test against (though I should set one up).
> > >
> > > When we know where the reset comes from maybe we can devise a workaround.
> > >
> > > Cheers,
> > > Cameron Simpson <cs at cskk.id.au>
> >
> > It's worse without screen:
> >
> > console: both colours and cursor reset
> > screen: only cursor resets
> >
> > Screen on its own is fine with my cursor and colours. I'm using
> > screen 99% of the time.
> >
> > Vim also resets the cursor, but the colours are fine, both in and out
> > of screen.
>
> I have found a kind of workaround now:
>
> TERM=xterm-color mutt
>
> However this means that the cursor is visible in menus and such. Not
> really a big problem. I'd rather that than have to keep applying my
> cursor settings every so often.

Spoke a bit too soon there. Now mutt doesn't recognise my home, end
and delete keys, probably because of reading a different terminfo I
guess.

I tried entering raw mappings in the config with vim's Ctrl-V method,
but it doesn't see those either. Is there a way around that?

--
Dave

Mathematicians are like Frenchmen: whatever you say to them they
translate into their own language, and forthwith it is something
entirely different.
    -- Johann Wolfgang von Goethe

                                                            .--.  oo
                                                           (____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'