Right. I deeply question that logic though. The fact that a corrupted save
bug was fixed is sort of a game changer from a usability perspective. I
mean, if it wasn't well known, well documented, or fixed, I might say that
it makes sense but as it stands, releasing code that has a known
Hi,
On Fri, Jul 3, 2015 at 3:53 PM, Enrico Forestieri for...@lyx.org wrote:
Your patch still does not work on Windows. It may work when files have
names encodable in the current code page, otherwise it fails.
Note that NTFS uses UTF-16 even if python returns msbc as the filesystem
encoding.
On 07/04/2015 04:09 PM, Benedict Holland wrote:
Right. I deeply question that logic though. The fact that a corrupted
save bug was fixed is sort of a game changer from a usability
perspective. I mean, if it wasn't well known, well documented, or
fixed, I might say that it makes sense but as it
Le 30/06/2015 19:20, Enrico Forestieri a écrit :
On Tue, Jun 30, 2015 at 06:14:05PM +0100, Guillaume M-M wrote:
Dear list,
I got an assertion in stable (1b596e92) for the second time today. It
happened while selecting text (first time with Shift+Arrows and second time
with the mouse).
I
I have no experience with how this is supposed to work, but I would like
to confirm that this behavior is expected:
1. In Tools Preferences Language Settings, set Cursor movement to
Logical (by the way, a tooltip here might be useful).
2. Open the attached file.
3. In Arabic, when I press
I have no experience with how this is supposed to work, but I would like
to confirm that this behavior is expected:
1. In Tools > Preferences > Language Settings, set "Cursor movement" to
"Logical" (by the way, a tooltip here might be useful).
2. Open the attached file.
3. In Arabic, when I press
Hi,
On Fri, Jul 3, 2015 at 3:53 PM, Enrico Forestieri wrote:
> Your patch still does not work on Windows. It may work when files have
> names encodable in the current code page, otherwise it fails.
> Note that NTFS uses UTF-16 even if python returns "msbc" as the filesystem
>
Right. I deeply question that logic though. The fact that a corrupted save
bug was fixed is sort of a game changer from a usability perspective. I
mean, if it wasn't well known, well documented, or fixed, I might say that
it makes sense but as it stands, releasing code that has a known
On 07/04/2015 04:09 PM, Benedict Holland wrote:
Right. I deeply question that logic though. The fact that a corrupted
save bug was fixed is sort of a game changer from a usability
perspective. I mean, if it wasn't well known, well documented, or
fixed, I might say that it makes sense but as it
Le 30/06/2015 19:20, Enrico Forestieri a écrit :
On Tue, Jun 30, 2015 at 06:14:05PM +0100, Guillaume M-M wrote:
Dear list,
I got an assertion in stable (1b596e92) for the second time today. It
happened while selecting text (first time with Shift+Arrows and second time
with the mouse).
I
10 matches
Mail list logo