octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #61006] CTRL+V in Commad Window with encoding


From: Przemek
Subject: [Octave-bug-tracker] [bug #61006] CTRL+V in Commad Window with encoding CP1250 hang Command Window
Date: Tue, 3 Aug 2021 13:47:31 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

URL:
  <https://savannah.gnu.org/bugs/?61006>

                 Summary: CTRL+V in Commad Window with encoding CP1250 hang
Command Window
                 Project: GNU Octave
            Submitted by: psiedlaczek
            Submitted on: Tue 03 Aug 2021 05:47:29 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: psiedlaczek
        Originator Email: 
             Open/Closed: Open
                 Release: 6.3.0
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

 
As in title. I observed in Octave 6.3.0 that when I using my default Windows
10 system encoding CP1250 and paste by CTRL+V the clipped text in to Command
Window it hang the Command Window completelly and restart of Octave is needed.
Example below:



c=1; # słownik: lower and uppercase żłóęąźń朌яŻĘĄĆŁ ...
"CP1250 chars called by combination RALT+N C Z X S O ... "


 
The chars can be located in a variable, string or in comment. 
This happens also when using paste from mouse quick menu.

Some remedion is to set Editor preferences for new files to other encoding
e.g. US-ASCII; use comments without national charters; in english ; or convert
*.m files to plain ASCII.

However I would be happy to have comments in natural language wihout these
inconveniences ;) 






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61006>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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