[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 --- Comment #12 from Erik Quaeghebeur --- (In reply to Waqar Ahmed from comment #11) > You can just check the help command, it would have saved you from writing > such a long comment. > > kate -b # run in blocking mode Thanks for pointing out that is the option I need. For the record: (In reply to Erik Quaeghebeur from comment #10) > […] From the help, I see no option that would be the one I need. […] I did read the help. It did not help me, as I explicitly mentioned. The help text for that option (translated from Dutch) is “If using an already running kate process, block until ready, if URLs to open have been given.” and not “Run in blocking mode.”. In the context of my comment, there is no ‘already running kate process’. So I guess the help text could be improved. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 --- Comment #11 from Waqar Ahmed --- You can just check the help command, it would have saved you from writing such a long comment. kate -b # run in blocking mode -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #10 from Erik Quaeghebeur --- (In reply to Waqar Ahmed from comment #9) > https://invent.kde.org/utilities/kate/-/merge_requests/1151 Apparently this feature was merged and made the default silently. It apparently is in the version that my distro has recently started shipping. This new ‘feature’ breaks my setup, where I launch kate from a Python script using subprocess as part of a kmail filter. Because subprocess now thinks kate has finished (it gets the pid of the intermediate process, not of the kate instance itself), it doesn't block anymore and the script does not work anymore. :-( (In reply to Christoph Cullmann from comment #6) > I have no issue if we have this as option, one can then still think about > what should be the default. I do hope there is an option to get the previous behavior back, as otherwise a regression was introduced breaking functionality just for the sake of getting rid of some visual annoyance. From the help, I see no option that would be the one I need. Please advise to at least get a workaround until the regression reverted or an option is added (which'll still take months to propagate to my distro). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Waqar Ahmed changed: What|Removed |Added Version Fixed In||23.04 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED CC||waqar@gmail.com Resolution|--- |FIXED --- Comment #9 from Waqar Ahmed --- https://invent.kde.org/utilities/kate/-/merge_requests/1151 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 --- Comment #8 from Justin Zobel --- Starting kate with kstart5 gives some warning output: `Omitting both --window and --windowclass arguments is not recommended` As this automatically forks kate into it's own process instead of running inside the terminal an alias would then do it fine. alias kate='kstart5 kate` Have tested with kstart5 kate myfile and that opens the file correctly. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #7 from Nate Graham --- Also when you want to launch a KDE app from the terminal, the best way is to do `kstart5 ` This goes through the standard startup sequence, which means yu get launch feedback and the app gets put into its own cgroup slice so that it appears correctly in System Monitor. Perhaps kate could do this automatically and re-launch itself when run directly? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #6 from Christoph Cullmann --- I have no issue if we have this as option, one can then still think about what should be the default. For the debugging output: with the latest frameworks release of this month and some recent Kate, normally there shall be no output for release builds. But in previous versions there was always some crap output ;) (and there might still be some if you run outside of a KDE Plasma session) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Reid changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #5 from Reid --- There's nothing really "wrong" with the current behaviour, however I do agree with this changing simply to make things more consistent Currently Kate will detach if there's a running instance but won't if there's no running instance, and that can just throw some users off since the behaviour is just not consistent, or at least not as consistent as it could be, so I can see why some would want the default behaviour changed and move the current behaviour to a flag. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 --- Comment #4 from advaith --- quite frankly using & every time you open a file isn't a solution. its a workaround. there needs to be a at least a flag that can be used to allow kate to detach from a terminal and not output debug info -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Christoph Feck changed: What|Removed |Added Summary|Feature request: Kate |Kate should detach when |should detach when launched |launched from a terminal |from a terminal | Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
