[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #45610] wrong commenting (ctrl+R) behavior wit

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #45610] wrong commenting (ctrl+R) behavior with CRLF eols in GUI editor
Date: Sun, 25 Sep 2016 08:15:22 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40

Update of bug #45610 (project octave):

                 Release:                   4.0.0 => dev                    
        Operating System:       Microsoft Windows => Any                    
                 Summary: wrong commenting (ctrl+R) behavior in GUI editor
under Windows => wrong commenting (ctrl+R) behavior with CRLF eols in GUI


Follow-up Comment #19:

To be precise, this only happens with "CRLF" endings on *any* operating
system. With "LF" EOLs (mostly used in Octave) and "CR" EOLs the bug isn't

Dan's patch works, but only for Windows builds. It doesn't fix the issue for
Linux builds (I just tried) - I can imagine scenarios where someone edits
Matlab scripts from the Windows world on Linux that go back to Matlab on
Windows in a later stage.

>From the URL in comment #13 it seems this Qscintilla bug has been there for a
decade now. Do we still have hope it'll ever get fixed upstream?  Is there any
formal upstream Qscintilla bug report at all, or only the forum thread
mentioned in comment #13?

As an aside, I sometimes wonder why Ctrl-R introduces "%" rather than "##"
comments, as the latter is he convention in Octave. Did I overlook a setting

(==> title, OS & release adapted)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]