https://bugs.documentfoundation.org/show_bug.cgi?id=162873

--- Comment #4 from Dave Lovelace <[email protected]> ---
(In reply to Dave Lovelace from comment #3)
> (In reply to m_a_riosv from comment #1)
> > Have you verified if it is defined in Menu>Tools>Customize>Keyboard?
> > 
> > Please test in safe mode, Menu/Help/Restart in Safe Mode
> 
> I have now done so.  I had not previously, because (1) I never had even seen
> this section (Menu>Tools>Customize>Keyboard) before and didn't know it
> existed, (2) in researching the problem (information on non-breaking spaces)
> NOT ONE TIME was this mentioned as something that needed to be set up, and
> (3) why would an update to a new rev change any settings of this sort?  But
> at any rate, for Ctrl+Shift+Space it shows "Insert No-break space".
> 
> And as I noted (admittedly since your reply), I discovered that previously
> existing no-break spaces are now gone.  From my point of view, this is a
> serious problem.

Hmph!  I did as you asked, and restarted in safe mode.  Empty document.  I
entered a bunch of individual letters, separating some with ctrl-shift-space,
some with spaces, then entered text at the very beginning until they started
wrapping off the right margin.  Contrary to what I observed earlier, the groups
separated with no-break spaces did wrap together.  I went back to normal mode,
and observed the same.  I don't know whether things changed between my two
tests or whether my observations were wrong the first time.  I incline toward
the latter, but don't know whether opening in safe mode could affect this (even
after returning to normal mode).

HOWEVER, I am unable to tell by looking whether the no-break spaces are there
or not.  According to everything I found (first round of research), what
controls this is View->Field Shadings.  It doesn't matter whether that is
checked or not; no shading shows.

So do I need to enter another bug report to get THAT in?  I really do need to
be able to see whether these things (both non-breaking hyphens and non-breaking
spaces) are correctly present.

(I'll add that this is a good example of why I always hesitate to up-rev.  In
my experience, it ALWAYS breaks something that was working.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to