[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if e
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action |
Date: |
Sat, 11 Nov 2017 05:03:06 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Follow-up Comment #7, bug #52361 (project octave):
Torsten, I seem to have induced a little thread drift :-)
Yes it is esp. the window position that is problematic across versions - older
Octave releases often have the title bar above the upper screen limits so I
cannot even move them down.
Still I think (but it's just my opinion) that settings files shouldn't be
shared across versions for any piece of SW.
What if I want to test a dev version w/o screwing up settings for a stable
release? How to check if installation of a new mxe-octave binary including
default qt settings works w/o problems, w/o affecting installed releases?
I suppose having several Octave versions installed side-by-side is mainly a
developer situation, but not quite limited to developers.
Currently I have several qt-settings file backups in .config/octave/ , one for
each Octave release/version so I can at least restore my personal settings w/o
going through several pref tabs. It works but is sub-optimal at best.
OK, next Monday at work I'll see if my "fix" in comment #3 works there as
well. If so I'll close this report.
Thanks for you attention.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?52361>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/07
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/09
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/09
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/10
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/10
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/10
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/11
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/11
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/11
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/11
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/11
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/12
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Philip Nienhuis, 2017/11/22
- [Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action, Torsten, 2017/11/23