Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.thunderbird > #21269 > unrolled thread

Backspace weirdness

Back to article view | Back to alt.comp.software.thunderbird

Contents

  Backspace weirdness The Real Bev <bashley101@gmail.com> - 2026-07-05 10:20 -0700
    Re: Backspace weirdness "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-07-05 20:24 +0100
      Re: Backspace weirdness Andy Burns <usenet@andyburns.uk> - 2026-07-05 20:33 +0100
        Re: Backspace weirdness The Real Bev <bashley101@gmail.com> - 2026-07-06 11:44 -0700
          Re: Backspace weirdness "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-07-06 20:51 +0100
          Re: Backspace weirdness Andy Burns <usenet@andyburns.uk> - 2026-07-06 20:57 +0100
            Re: Backspace weirdness Nobody <jock@soccer.com> - 2026-07-06 16:23 -0700

#21269 — Backspace weirdness

When I updated TB/linux from 68 to 138 (don't ask!) the backspace was 
converted to CRLFs at the end of the message but before the .sig.  After 
a reasonable amount of editing I had to delete a LOT of generated 
whitespace. Shift-backspace solved the problem, but that seems like a 
Nextdoor-level stupidity.  WTF?

-- 
Cheers, Bev
   Some people just can't be helped; you take 'em out of the rat race
   for 5 minutes and they end up missing the rats!       --XR650LDave

[toc] | [next] | [standalone]

#21274

On 2026/7/5 18:20:58, The Real Bev wrote:
> When I updated TB/linux from 68 to 138 (don't ask!) the backspace was 
> converted to CRLFs at the end of the message but before the .sig.  After 
> a reasonable amount of editing I had to delete a LOT of generated 
> whitespace. Shift-backspace solved the problem, but that seems like a 
> Nextdoor-level stupidity.  WTF?
> 
Not sure what you mean by "backspace"; to me that means
cursor-moves-to-left-one-space, control-H, left tab, character 8 - often
used as delete-to-left (though strictly I prefer to think of that as
character 127, alias backspace-space-backspace).

When I started using TB again after decades, I came in at about 138, and
found quite a lot of weird behaviours at end of lines (and between the
body and the .sig separator line); they mostly cleared up in the next
few versions (I'm currently on 140.11.1esr), though not all (it still
gets confused between quoted [blue] text and new [black], and sometimes
inserts _two_ newlines when I press resturn, but I'm used to that now) -
it's still a lot better than only a few versions ago.
-- 
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

And on the question of authorship, I subscribe to the view that the
plays were not in fact written by Shakespeare but by someone of the
same name. - Hugh Bonneville (RT 2014/10/11-17)

[toc] | [prev] | [next] | [standalone]

#21276

J. P. Gilliver wrote:

> When I started using TB again after decades, I came in at about 138, and
> found quite a lot of weird behaviours at end of lines (and between the
> body and the .sig separator line); they mostly cleared up in the next
> few versions (I'm currently on 140.11.1esr), though not all (it still
> gets confused between quoted [blue] text and new [black], and sometimes
> insertstwo newlines when I press resturn, but I'm used to that now) -
> it's still a lot better than only a few versions ago.

I think v115 (The supernova GUI rewrite) introduced several of the 
oddities, I still occasionally have to tidy up whitespace where I've 
interspersed my reply inside quoted text lines (and I sometimes cock 
that up and get stray chevrons).

[toc] | [prev] | [next] | [standalone]

#21298

On 7/5/26 12:33, Andy Burns wrote:
> J. P. Gilliver wrote:
> 
>> When I started using TB again after decades, I came in at about 138, and
>> found quite a lot of weird behaviours at end of lines (and between the
>> body and the .sig separator line); they mostly cleared up in the next
>> few versions (I'm currently on 140.11.1esr), though not all (it still
>> gets confused between quoted [blue] text and new [black], and sometimes
>> insertstwo newlines when I press resturn, but I'm used to that now) -
>> it's still a lot better than only a few versions ago.
> 
> I think v115 (The supernova GUI rewrite) introduced several of the
> oddities, I still occasionally have to tidy up whitespace where I've
> interspersed my reply inside quoted text lines (and I sometimes cock
> that up and get stray chevrons).

Stuff is supposed to improve with time and effort, not degrade.  The 
Mozilla stuff doesn't seem to follow that rule.  I'm sure I can find an 
improvement if I think about it long enough, but the degradations are 
obvious.

Stuff is faster now, of course, but that may just be due to connection 
speed -- for which mozilla can't take credit.

-- 
Cheers, Bev
      "To turn is to admit defeat."   -- Hugh Grierson

[toc] | [prev] | [next] | [standalone]

#21301

On 2026/7/6 19:44:41, The Real Bev wrote:
> On 7/5/26 12:33, Andy Burns wrote:
>> J. P. Gilliver wrote:
>>
>>> When I started using TB again after decades, I came in at about 138, and
>>> found quite a lot of weird behaviours at end of lines (and between the
>>> body and the .sig separator line); they mostly cleared up in the next
>>> few versions (I'm currently on 140.11.1esr), though not all (it still
>>> gets confused between quoted [blue] text and new [black], and sometimes
>>> insertstwo newlines when I press resturn, but I'm used to that now) -
>>> it's still a lot better than only a few versions ago.
>>
>> I think v115 (The supernova GUI rewrite) introduced several of the
>> oddities, I still occasionally have to tidy up whitespace where I've
>> interspersed my reply inside quoted text lines (and I sometimes cock
>> that up and get stray chevrons).
> 
> Stuff is supposed to improve with time and effort, not degrade.  The 
> Mozilla stuff doesn't seem to follow that rule.  I'm sure I can find an 
> improvement if I think about it long enough, but the degradations are 
> obvious.
> 
> Stuff is faster now, of course, but that may just be due to connection 
> speed -- for which mozilla can't take credit.
> 
Well, for me, most (not all) of the bugs in the compose editor were
fixed between (about) 132 and 140.
-- 
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

I hope you dream a pig.

[toc] | [prev] | [next] | [standalone]

#21302

The Real Bev wrote:

> Andy Burns wrote:
>
>> I think v115 (The supernova GUI rewrite) introduced several of the
>> oddities
> 
> Stuff is supposed to improve with time and effort, not degrade.  The 
> Mozilla stuff doesn't seem to follow that rule. 
AIUI large chunks of the code had become difficult to maintain, and were 
re-written for supernova, a few features were lost in the process (e.g. 
the lines that draw the thread tree)

[toc] | [prev] | [next] | [standalone]

#21306

On Mon, 6 Jul 2026 20:57:48 +0100, Andy Burns <usenet@andyburns.uk>
wrote:

>The Real Bev wrote:
>
>> Andy Burns wrote:
>>
>>> I think v115 (The supernova GUI rewrite) introduced several of the
>>> oddities
>> 
>> Stuff is supposed to improve with time and effort, not degrade.  The 
>> Mozilla stuff doesn't seem to follow that rule.

>AIUI large chunks of the code had become difficult to maintain, and were 
>re-written for supernova, a few features were lost in the process (e.g. 
>the lines that draw the thread tree)

Which supposedly can be restored by adding the following to a
userChrome.css file.  

-----------

#threadTree treechildren::-moz-tree-line {
    visibility: visible !important;
}

-----------

Lack of lines doesn't bother me... so I haven't tried it.
  
Interestingly, attribution for the code shows as being from
'ilias.ca'.  Oh, possibly Chris who ruled the olde Mozilla TB and Ffox
boards while flailing a morning star!  <g>

[toc] | [prev] | [standalone]

Back to top | Article view | alt.comp.software.thunderbird

csiph-web