Steffen Daode Nurpmeso dixit:

>Yeaaah... the user experience would be even better if the website
>would describe how to subscribe to miros-mksh@.

I just committed a textual change that should make that
even clearer.

>It's all fine now!  Great!
>And looking forward for a bright, resurrected R49!

You’re welcome ;-) Although this will be R48, I think.
Can you confirm that…

>Well, the minimal code to reproduce is
[…]
>          signal(SIGINT, &onsig);
>          kill(getpid(), SIGINT);

… this issue is no longer a problem, then?

> |• long job names
>
>Ja-ah (but
[…]
>is really a good thing to have!)

Okay, I cave in ;-) you get 256 now. Should be enough for
almost all screen and terminal sizes (unless you’re gecko2@
and run one xterm in *his* font size across all *three* of
the wide-screen monitors he’s got on his desktop at the dayjob).

That’s commitid 10051F2DD2B49D415C3.

> |I’ve not got any of yours on my radar atm… did I forget some?
>
>Well, it's only minor convenience shit for me, like

>the „expansion in the middle of a word“

As I explained, I strongly consider this a feature and use
it almost daily, if not daily.

>„when traversing history $COLUMNS
>should be used fully, not `WIDTH % $COLUMNS', when displaying
>linee with `WIDTH > $COLUMNS'”.

That’s commitid 10051F2DD36363A1B44 which is massively complex
(also because it makes Emacs and Vi share code and data, which
is a prerequisite for some of this, along with lots of cleanup
etc.) and may break stuff (interactive, not testsuit’able).

@everyone: please do test these changes! (The fix is for Emacs
mode only but Vi mode prompt length calculation and other code
and data references are affected, so please test that Vi isn’t
changed at all and Emacs gets this fixed.)

The new code is a bit more clueful and tries to fill the screen
up to 2/3 of $COLUMNS, including the prompt if any. If we would
hit the prompt when displaying, we scroll out the first char so
don’t be surprised about that if you happen onto it.

>Shitty stuff like that...

As you can see, not everything gets fixed, and especially not
immediately, but bringing things to my attention every now and
then surely helps.

Now drink something to celebrate ;-)

bye,
//mirabilos

PS: I’ll need to write changelog entries and do mirror pushes
    and website recompilation, so gimme a few minutes before
    this is publicly visible. As usual.
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
        -- Thomas E. Dickey on the Lynx mailing list, about OpenSSL

Reply via email to