[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)

2024-05-24 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=486061

--- Comment #6 from Gerald Senarclens de Grancy  ---
Thanks for your investigation Igor! When vacation time starts I'll have another
look and will attempt a MR if I can up with a reasonable improvement.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)

2024-05-02 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=486061

--- Comment #3 from Gerald Senarclens de Grancy  ---
True that existing configurations that work around the problem would break by
fixing this issue. Not sure how many people this would affect. For new users,
the current behavior is misleading as they're defining cli arguments and should
be able to presume that they are passed to the cli as if they were typed in a
konsole window.
A possible alternative to using the argument text input as a raw string would
be to add a proper help message telling the user which characters require
escaping.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)

2024-04-24 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=486061

Gerald Senarclens de Grancy  changed:

   What|Removed |Added

 CC||o...@senarclens.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486061] New: Launch configuration arguments are not fully passed when executing (escaped)

2024-04-24 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=486061

Bug ID: 486061
   Summary: Launch configuration arguments are not fully passed
when executing (escaped)
Classification: Applications
   Product: kdevelop
   Version: 5.12.230801
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: o...@senarclens.eu
  Target Milestone: ---

Created attachment 168859
  --> https://bugs.kde.org/attachment.cgi?id=168859=edit
5 screenshots showing the problem and a workaround

SUMMARY
When typing brackets in the launch configuration arguments, these bracket
characters are ignored when executing that launch configuration (likely linked
to Bug 324830 which didn't describe the issue properly). However, they are used
for filtering automated test cases with the popular catch2 v3 library.

STEPS TO REPRODUCE
1. create launch configuration that uses square brackets, eg. "[capitalize]"
(see screenshots)
2. select this launch configuration as current launch configuration and execute
it

OBSERVED RESULT
the square brackets are silently removed from the argument; the run window
shows the argument without the brackets, eg.
"/home/gerald/repos/github/cpp/c_strings_solutions/build>
/home/gerald/repos/github/cpp/c_strings_solutions/build/c_strings_test
capitalize" when the argument was set to "[capitalize]". This means that
filtering test cases by tags
using the catch2 library is not possible without a workaround.

EXPECTED RESULT
The execution gets the full string passed into the arguments field. All
characters in the text field are passed 1:1.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kubuntu 23.10 with all updates but no backports
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
As a workaround, it is possible to escape the brackets with a "\", then they
are passed (however, the backlash is hence not passed as argument);

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 468455] New: Copying a file into a project with an existing name causes Kdevelop to stall

2023-04-13 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=468455

Bug ID: 468455
   Summary: Copying a file into a project with an existing name
causes Kdevelop to stall
Classification: Applications
   Product: kdevelop
   Version: 5.7.211203
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: file tree
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: o...@senarclens.eu
  Target Milestone: ---

Created attachment 158062
  --> https://bugs.kde.org/attachment.cgi?id=158062=edit
screencast demonstrating the problem

SUMMARY
Copying a file into a project with an existing name causes Kdevelop to stall


STEPS TO REPRODUCE
see attached screencast

1. open a project with multiple files
2. select copy on one of the files in the project view's file list
3. select paste in the project to paste the same file (in order to create a
copy under a new name)

OBSERVED RESULT
Kdevelop complains that the file already exists. It opens a dialog offering to
enter a new filename. It is not possible to change the name in the dialog, the
dialog cannot be closed with either "Cancel" or "X" or any other action.
Kdevelop cannot be closed either. The program stalls.
Workaround: cancel the copy via the notifications popup (if one is present).

EXPECTED RESULT
The user can enter a new filename. The copied file is also available under the
new filename.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04 w/ all regular updates (backports not
activated)
(available in About System)
KDE Plasma Version: plasmashell 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
please see attached screencast

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 313677] Cannot undo auto undesired (auto)completion

2023-01-12 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=313677

Gerald Senarclens de Grancy  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 313677] Cannot undo auto undesired (auto)completion

2022-12-27 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=313677

--- Comment #7 from Gerald Senarclens de Grancy  ---
Created attachment 154846
  --> https://bugs.kde.org/attachment.cgi?id=154846=edit
screencast showing how the completion is automatically redone

unfortunately, the problem still reproduces as of 2022-12-27

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 313677] Cannot undo auto undesired (auto)completion

2022-12-27 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=313677

--- Comment #6 from Gerald Senarclens de Grancy  ---
Created attachment 154844
  --> https://bugs.kde.org/attachment.cgi?id=154844=edit
added screenshot showing that `fastex` must be enabled to trigger the example
shown in the bug description

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 411096] Kdevelop crashed when opening previous session (with a single Python 3 project)

2022-09-24 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=411096

--- Comment #2 from Gerald Senarclens de Grancy  ---
I have literally no idea about the project or setup I was working on when the
crash occurred three years ago. Feel free to close.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 416267] Space bar does not work when markdown preview is open

2020-01-14 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=416267

Gerald Senarclens de Grancy  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages
 CC||o...@senarclens.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 416267] New: Space bar does not work when markdown preview is open

2020-01-14 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=416267

Bug ID: 416267
   Summary: Space bar does not work when markdown preview is open
   Product: kate
   Version: 19.12.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plugin-preview
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: o...@senarclens.eu
  Target Milestone: ---

Created attachment 125129
  --> https://bugs.kde.org/attachment.cgi?id=125129=edit
short screencast demonstrating the problem

SUMMARY
It is not possible to enter 'space' when the preview sidebar is open during
markdown input.

STEPS TO REPRODUCE
1. Open any markdown (.md) document in Kate
2. Make sure the "Document Preview" plugin is enabled in
   Settings->Configure Kate -> Plugins
3. Open the document preview
4. Continue typing in the markdown document

OBSERVED RESULT
Almost all input keys are accepted, but using the space bar does not insert
space characters. This is true both for normal mode and vi input.

EXPECTED RESULT
All keyboard keys should insert their respective characters into the document
when pressed, regardless of the markdown preview being shown or not.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.17 User Edition
(available in About System)
Kate Version: 19.12.1
Okular Version: 1.9.1
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 411096] New: Kdevelop crashed when opening previous session (with a single Python 3 project)

2019-08-20 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=411096

Bug ID: 411096
   Summary: Kdevelop crashed when opening previous session (with a
single Python 3 project)
   Product: kdevelop
   Version: 5.4.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: o...@senarclens.eu
  Target Milestone: ---

Application: kdevelop (5.4.0)

Qt Version: 5.12.3
Frameworks Version: 5.61.0
Operating System: Linux 4.15.0-58-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
- What I was doing when the application crashed:

started kdevelop with a previously loaded Python 3 project; the crash only
happend once (did not reproduce after clearing the cache); hope the stacktrace
will be useful

The crash does not seem to be reproducible.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
[Current thread is 1 (Thread 0x7fc5cf773bc0 (LWP 17040))]

Thread 20 (Thread 0x7fc52f7fe700 (LWP 17428)):
#0  0x7fc5c4a2f9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x557e8e4162c0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x557e8e416270,
cond=0x557e8e416298) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x557e8e416298, mutex=0x557e8e416270) at
pthread_cond_wait.c:655
#3  0x7fc5cc433dbb in QWaitConditionPrivate::wait (deadline=...,
this=0x557e8e416270) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x557e8e3ef7b0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fc5cc4340c9 in QWaitCondition::wait (this=0x557e8e419528,
mutex=0x557e8e3ef7b0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#6  0x7fc5c262ac8b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x557e8e417c20, th=) at ./src/weaver.cpp:594
#7  0x7fc5c262b925 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait
(this=0x557e8e417c20, th=, th@entry=0x7fc5280021e0,
threadWasBusy=threadWasBusy@entry=true,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ./src/weaver.cpp:554
#8  0x7fc5c262f7d8 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x557e8e36a670, th=0x7fc5280021e0, wasBusy=) at
./src/workinghardstate.cpp:66
#9  0x7fc5c262abed in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fc5280021e0, wasBusy=) at ./src/weaver.cpp:568
#10 0x7fc5c262d69b in ThreadWeaver::Thread::run (this=0x7fc5280021e0) at
./src/thread.cpp:103
#11 0x7fc5cc42cc72 in QThreadPrivate::start (arg=0x7fc5280021e0) at
thread/qthread_unix.cpp:361
#12 0x7fc5c4a296db in start_thread (arg=0x7fc52f7fe700) at
pthread_create.c:463
#13 0x7fc5cbd2c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7fc52700 (LWP 17427)):
#0  0x7fc5c4a2f9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x557e8e4162c0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x557e8e416270,
cond=0x557e8e416298) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x557e8e416298, mutex=0x557e8e416270) at
pthread_cond_wait.c:655
#3  0x7fc5cc433dbb in QWaitConditionPrivate::wait (deadline=...,
this=0x557e8e416270) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x557e8e3ef7b0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fc5cc4340c9 in QWaitCondition::wait (this=0x557e8e419528,
mutex=0x557e8e3ef7b0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#6  0x7fc5c262ac8b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x557e8e417c20, th=) at ./src/weaver.cpp:594
#7  0x7fc5c262b925 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait
(this=0x557e8e417c20, th=, th@entry=0x7fc5340025e0,
threadWasBusy=threadWasBusy@entry=true,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ./src/weaver.cpp:554
#8  0x7fc5c262f7d8 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x557e8e36a670, th=0x7fc5340025e0, wasBusy=) at
./src/workinghardstate.cpp:66
#9  0x7fc5c262abed in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fc5340025e0, wasBusy=) at ./src/weaver.cpp:568
#10 0x7fc5c262d69b in ThreadWeaver::Thread::run (this=0x7fc5340025e0) at
./src/thread.cpp:103
#11 0x7fc5cc42cc72 in QThreadPrivate::start (arg=0x7fc5340025e0) at
thread/qthread_unix.cpp:361
#12 0x7fc5c4a296db in start_thread (arg=0x7fc52700) at
pthread_create.c:463
#13 

[frameworks-ktexteditor] [Bug 386151] Error using Tools->Scripts->Emmet

2018-12-12 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=386151

Gerald Senarclens de Grancy  changed:

   What|Removed |Added

 CC||o...@senarclens.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 400294] SigSegFault in background parser [crash in Php::ExpressionVisitor::visitStaticMember(Php::StaticMemberAst*)]

2018-12-05 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=400294

--- Comment #8 from Gerald Senarclens de Grancy  ---
@Kevin: any idea when 5.3.1 (including this fix) will be released?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 400294] SigSegFault in background parser [crash in Php::ExpressionVisitor::visitStaticMember(Php::StaticMemberAst*)]

2018-11-27 Thread Gerald Senarclens de Grancy
https://bugs.kde.org/show_bug.cgi?id=400294

Gerald Senarclens de Grancy  changed:

   What|Removed |Added

 CC||o...@senarclens.eu

-- 
You are receiving this mail because:
You are watching all bug changes.