Use dashes (vertically centered) for Beamer's pause LabelString?

2021-02-22 Thread Scott Kostyshak
We currently use the underscore for the LabelString of the pause layout.
The dash seems a little more pleasing to me since it is vertically
centered. I do wish the width of the dash was as long as the underscore
though. I think I would most prefer something like an em-dash but I
don't think we use unicode in the LabelString.

Any thoughts on the attached patch and screenshots?

Scott
From ba0106ea5890d07a1825f9625b0b6c41e9345bc0 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak 
Date: Fri, 19 Feb 2021 00:44:25 -0500
Subject: [PATCH] Use dash for Beamer's pause label string

The dash is vertically centered.
---
 lib/layouts/beamer.layout | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/layouts/beamer.layout b/lib/layouts/beamer.layout
index a26c409783..e6ebed654a 100644
--- a/lib/layouts/beamer.layout
+++ b/lib/layouts/beamer.layout
@@ -764,7 +764,7 @@ Style Pause
   LabelTypeStatic
   LabelBottomSep   0
   LeftMargin   M
-  LabelString  "_ _ _ _ _ _ _ _ _ _ _ _ _ _"
+  LabelString  "---"
   LabelFont
 Family typewriter
 Series Medium
-- 
2.20.1



signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: lyx master crashed when converting text to note

2021-02-22 Thread Jean-Marc Lasgouttes
Le 22 février 2021 22:45:38 GMT+01:00, Pavel Sanda  a écrit :
>On Mon, Feb 22, 2021 at 06:31:08PM +, V K wrote:
>> Yes, I can recreate crash with anonymized file. I marked line/paragraph part 
>> of which should be selected before creating note to get a crash with . 
>> Selection should be from the first line. Selection should encompass one line 
>> more on the bottom if selecting from the second line from the top. That is 
>> the minimal length to get a crash.
>
>Indeed, I can reproduce the problem, generally selecting line starting with 
>== to the very end of the document and then insert-note is enough to 
>trigger it.
>
>Bisect leads to:
>commit 5a58ca6576a1fa2d6bea8e9e7927d5779943e593
>Author: Jean-Marc Lasgouttes 
>Date:   Sun Feb 14 21:34:43 2021 +0100
>
>Fix caret height when inserting new inset
 

Thanks for tracking this. I'll have look next week.

JMarc
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: lyx master crashed when converting text to note

2021-02-22 Thread Pavel Sanda
On Mon, Feb 22, 2021 at 06:31:08PM +, V K wrote:
> Yes, I can recreate crash with anonymized file. I marked line/paragraph part 
> of which should be selected before creating note to get a crash with . 
> Selection should be from the first line. Selection should encompass one line 
> more on the bottom if selecting from the second line from the top. That is 
> the minimal length to get a crash.

Indeed, I can reproduce the problem, generally selecting line starting with 
== to the very end of the document and then insert-note is enough to 
trigger it.

Bisect leads to:
commit 5a58ca6576a1fa2d6bea8e9e7927d5779943e593
Author: Jean-Marc Lasgouttes 
Date:   Sun Feb 14 21:34:43 2021 +0100

Fix caret height when inserting new inset

For now, the simplest thing to do it to compute metrics in all cases
before calling setCurrentFont().

In 2.5, a better approach will be to add a new virtual function
InsetText::setFont that will set correctly TextMetrics::font_ (a cache
of the reference font).

Fixes bug #12126.


Backtrace:
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x76558535 in __GI_abort () at abort.c:79
#2  0x769247bd in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x562d6fef in 
std::__debug::vector<__gnu_debug::_Safe_iterator,
 std::__debug::list > >, 
std::allocator<__gnu_debug::_Safe_iterator,
 std::__debug::list > > > 
>::operator[] (this=0x7fffec009690, __n=37) at 
/usr/include/c++/8/debug/vector:417
#4  0x562d4acd in lyx::RandomAccessList::operator[] 
(this=0x7fffec009660, pos=37)
at ./support/RandomAccessList.h:161
#5  0x566295a8 in lyx::TextMetrics::checkInsetHit (this=0x581bdef8, 
pit=37, x=179, y=6)
at TextMetrics.cpp:1491
#6  0x566299ef in lyx::TextMetrics::checkInsetHit (this=0x581bdef8, 
x=179, y=6)
at TextMetrics.cpp:1515
#7  0x5668518a in lyx::BufferView::getCoveringInset 
(this=0x582f8430, text=..., x=179, y=6)
at BufferView.cpp:2303
#8  0x566852b1 in lyx::BufferView::updateHoveredInset 
(this=0x582f8430) at BufferView.cpp:2334
#9  0x5667ab85 in lyx::BufferView::processUpdateFlags 
(this=0x582f8430, 
flags=lyx::Update::SinglePar) at BufferView.cpp:574
#10 0x565ee806 in lyx::Text::dispatch (this=0x7fffec009658, cur=..., 
cmd=...) at Text3.cpp:2090
#11 0x569958a6 in lyx::InsetText::doDispatch (this=0x7fffec009640, 
cur=..., cmd=...)
at insets/InsetText.cpp:343
#12 0x568260b8 in lyx::Inset::dispatch (this=0x7fffec009640, cur=..., 
cmd=...) at insets/Inset.cpp:328
#13 0x56407754 in lyx::Cursor::dispatch (this=0x5836a088, cmd0=...) 
at Cursor.cpp:823
#14 0x56a2e35f in lyx::frontend::GuiView::dispatchToBufferView 
(this=0x57e02c30, cmd=..., dr=...)
at GuiView.cpp:3943
#15 0x56a3307b in lyx::frontend::GuiView::dispatch 
(this=0x57e02c30, cmd=..., dr=...)
at GuiView.cpp:4661
#16 0x569da4be in lyx::frontend::GuiApplication::dispatch 
(this=0x57424ff0, cmd=..., dr=...)
at GuiApplication.cpp:2211
#17 0x569d5dc8 in lyx::frontend::GuiApplication::dispatch 
(this=0x57424ff0, cmd=...)
at GuiApplication.cpp:1500
#18 0x564e9b1f in lyx::dispatch (action=...) at LyX.cpp:1477
#19 0x56a98a82 in lyx::frontend::Action::action (this=0x581cdf90) 
at Action.cpp:91
#20 0x56a98af8 in lyx::frontend::Action::qt_static_metacall 
(_o=0x581cdf90, 


Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] By report autoconf 2.71 works, 2.70 is known to have compatibility issues.

2021-02-22 Thread José Abílio Matos
On Monday, February 22, 2021 10:13:33 AM WET Pavel Sanda wrote:
> Anyone around with 2.70 installed to check whether the reported issues
> affect us? (Not a big deal, no sane distribution will deliver 2.70 with
> those issues as a default).
> 
> Pavel

Just as you said. In Fedora we will jump from 2.69 to 2.71. So I do not have 
2.70 at hand.
-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] By report autoconf 2.71 works, 2.70 is known to have compatibility issues.

2021-02-22 Thread Pavel Sanda
On Mon, Feb 22, 2021 at 11:07:04AM +0100, Pavel Sanda wrote:
> commit ddb8bd624af1493adea05e2e0a74d2a27f934e01
> Author: Pavel Sanda 
> Date:   Mon Feb 22 11:09:22 2021 +0100
> 
> By report autoconf 2.71 works, 2.70 is known to have compatibility issues.

Anyone around with 2.70 installed to check whether the reported issues
affect us? (Not a big deal, no sane distribution will deliver 2.70 with
those issues as a default).

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Feature Request for tex2lyx

2021-02-22 Thread Dr Eberhard Lisse
I case someone (on the Mac) has similar issues

find ~ \
 -not \( -path ~/Library -prune \) \
 -not \( -path ~/Downloads -prune \) \
 -not \( -path ~/.lyx -prune \) \
 -name '*.lyx' \
 -exec perl -i -p -e 's/\\language american/\\language english/g' {} ';'

does the trick.

greetings, el

On 22/02/2021 10:41, Dr Eberhard Lisse wrote:
> Than you for unconfusing me :-)-O
> 
> Seems I have been using "English (US) unnecessarily for years :-)-O
> 
> el
> 
> On 21/02/2021 18:55, Jürgen Spitzmüller wrote:
>> Am Sonntag, dem 21.02.2021 um 18:42 +0200 schrieb Dr Eberhard W Lisse:
>>> Enclosed the input and output from
>>>
>>> tex2lyx -c scrartcl mwe.tex
>>>
>>> mwe.lyx shows language "English" which in Babel terms is "british"
>>> whereas I would rather be able to set it to produce "English (USA)"
>>> which in babel terms would be "american".
>>
>> No, LyX has language "English" which in babel terms is "english" which
>> equals "american", not "british".
>>
>> Jürgen
>>
>>
> 
> 
> 


-- 
To email me replace 'nospam' with 'el'



signature.asc
Description: OpenPGP digital signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Feature Request for tex2lyx

2021-02-22 Thread Dr Eberhard Lisse
Than you for unconfusing me :-)-O

Seems I have been using "English (US) unnecessarily for years :-)-O

el

On 21/02/2021 18:55, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 21.02.2021 um 18:42 +0200 schrieb Dr Eberhard W Lisse:
>> Enclosed the input and output from
>>
>>  tex2lyx -c scrartcl mwe.tex
>>
>> mwe.lyx shows language "English" which in Babel terms is "british"
>> whereas I would rather be able to set it to produce "English (USA)"
>> which in babel terms would be "american".
> 
> No, LyX has language "English" which in babel terms is "english" which
> equals "american", not "british".
> 
> Jürgen
> 
> 


-- 
To email me replace 'nospam' with 'el'



signature.asc
Description: OpenPGP digital signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: activate another split view window by shortcut

2021-02-22 Thread Pavel Sanda
On Sun, Feb 21, 2021 at 10:22:05PM +, V K wrote:
> I checked new find ??? it's much more comfortable than previous! One thing 
> ??? after reaching end and continuing search from beginning by Enter active 
> is not search area but text area, so hitting Enter deletes matched word and 
> creates new paragraph in that place.

Juergen will know whether this was intended or no... Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel