[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 Eyal Rozenberg changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Eyal Rozenberg --- Not currently using amarok, and my hardware has changed, so can't reproduce this right now. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392247] Structure tree construction does not ignore sectioning within comment environment
https://bugs.kde.org/show_bug.cgi?id=392247 Eyal Rozenberg changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Eyal Rozenberg --- Still seeing this issue, now with Kile 2.9.93 . -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 --- Comment #4 from Eyal Rozenberg --- In those screenshot, I see a colored line under the tab. That's not sufficient, it should be possible to color the whole tab. The line is not noticeable enough. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 --- Comment #2 from Eyal Rozenberg --- (In reply to Podagric from comment #1) > it is now possible to do so. > could you close this bug? I'm not using the latest KDE right now, so I can't verify this being the case. But I won't object if someone verifies it and closes the bug. > and this is a duplicate of the bug > https://bugs.kde.org/show_bug.cgi?id=278699 Well, only partly, but it merits a different bug anyway. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409837] CMakeLists.txt doesn't check for presence of Embedded MariaDB
https://bugs.kde.org/show_bug.cgi?id=409837 Eyal Rozenberg changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Eyal Rozenberg --- I can no longer reproduce the bug with the version you specified. So, I'll close this as WORKSFORME. Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409837] CMakeLists.txt doesn't check for presence of Embedded MariaDB
https://bugs.kde.org/show_bug.cgi?id=409837 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Becker from comment #3) > As I wrote 2.9.71 (aka 2.10 Alpha1, you can get it from > https://download.kde.org/unstable/amarok/2.9.71/). git master works too and > isn't that different from the release yet. FYI: With this version, I'm getting a zillion CMake warnings: Package type "Amarok/ContextApplet" not found kf5.kcoreaddons.desktopparser: Unable to find service type for service "Amarok/ContextApplet" listed in "/usr/local/src/amarok-2.9.71/src/context/applets/wikipedia/package/metadata.desktop" -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409837] CMakeLists.txt doesn't check for presence of Embedded MariaDB
https://bugs.kde.org/show_bug.cgi?id=409837 --- Comment #2 from Eyal Rozenberg --- (In reply to Heiko Becker from comment #1) Which exact version should I try and build? -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 409966] Check if plugin install path is where the system expects them
https://bugs.kde.org/show_bug.cgi?id=409966 --- Comment #14 from Eyal Rozenberg --- Ah, I see what you mean. Ok then. That is, I'm not pleased but at least I understand the rationale of your decisions. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 409966] Check if plugin install path is where the system expects them
https://bugs.kde.org/show_bug.cgi?id=409966 --- Comment #12 from Eyal Rozenberg --- Excuse me, but - are you serious? This is the _Amarok_ bug tracking system. You can't close bugs about the current release and tell people not to use it. If that's how you feel - terminate your account or stop all activity on Amarok-related bugs. Are you trying to sabotage it or something? -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 409966] Check if plugin install path is where the system expects them
https://bugs.kde.org/show_bug.cgi?id=409966 --- Comment #10 from Eyal Rozenberg --- (In reply to Christophe Giboudeaux from comment #9) > Doesn't change anything. There's no officially supported Qt5 based amarok The single current official release of Amarok is 2.9.0. That's the one with this issue. That's the one that must be supported. If it uses KDE4 - fine, then that's what it uses. If it has issues then - fix them. You can't just ignore them because you don't like how the official version uses KDE4. I simply don't understand what you're talking about. And reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 409966] Check if plugin install path is where the system expects them
https://bugs.kde.org/show_bug.cgi?id=409966 Eyal Rozenberg changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #8 from Eyal Rozenberg --- (In reply to Christophe Giboudeaux from comment #7) > I recommend looking for a music player which is still maintained. I double-checked to ensure I wasn't missing a version 2.10 or 3.0 - and no, I wasn't. So, either Amarok is not maintained, period - which would be pretty sad; or v2.9 is maintained, albeit perhaps reluctantly and partially. Also - I can't just use the GitHub master branch, it depends on much newer versions of various libraries than typical distributions have . -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 409966] Check if plugin install path is where the system expects them
https://bugs.kde.org/show_bug.cgi?id=409966 --- Comment #6 from Eyal Rozenberg --- (In reply to Christophe Giboudeaux from comment #4) > why ecm ? isn't amarok 2.9 the KDE4 version? Can you explain the latest exchange of comments? I'm not quite following. Amarok 2.9 is the current release version, is it not? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409966] Amarok won't run, complains about missing plugins
https://bugs.kde.org/show_bug.cgi?id=409966 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #2 from Eyal Rozenberg --- (In reply to Christoph Feck from comment #1) > cmake is only a tool to _build_ the software. It's a tool to build the software so that it runs. > If you want to _run_ the > software, you should make sure you are installing it into directories where > the plugin loaders expect them, or adjust your environment variables > accordingly. I did make sure: I used -DCMAKE_INSTALL_PREFIX=/usr/local , which is perfectly valid and standard. I than used cmake to install. That installation should work. And if for some reason it can't (which shouldn't happen IMHO) - I should have been informed. I won't split hairs, so - I wouldn't have minded if it had been cmake install that gives some error or warning messages. > Please ask for help in a developer forum, mailing list, or IRC channel. But, again, I shouldn't need to: I did something very standard and straightfoward and the result was not as expected, without any warning/error messages up until installation. That _is_ a bug. Having said that - I did ask for help on the IRC channel, but none was extended. Which of the other two media would you suggest? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409966] New: Amarok won't run, complains about missing plugins
https://bugs.kde.org/show_bug.cgi?id=409966 Bug ID: 409966 Summary: Amarok won't run, complains about missing plugins Product: amarok Version: 2.9.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 I've downloaded and built Amarok 2.9.0 on Devuan Beowulf (= Debian Buster without systemd) - after installing a whole bunch of prerequisite Qt and KDE-related packaged. The build succeeds (after a bit of trouble I reported in other issues and got resolved); and I make install'ed amarok to /usr/loca . Now, when trying to run amarok, I get ``` amarok(24045)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType "Amarok/Plugin" not found ``` on the console, and a message box saying: > Amarok could not find any plugins. This indicates an installation problem. I'm reporting this as a bug for several reasons: 1. If something else need to be present on the system, then cmake'ing should have told me so. 2. Even if something is missing, the GUI and/or console messages should tell me what exactly what files, or folders, are missing so that I could go get them. 3. If plugins need to be installed independently - why aren't they available on the website? 4. If plugins are built and installed - how come amarok doesn't make even a minimal effort to locate them? Note: This is not resolved like the very similar problem I reported a while ago as the very similar bug 399097. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux KDE Plasma Version: 5.54.0-1 KDE Frameworks Version: Not sure what number to put here. Qt Version: 5.11.3+dfsg1-1 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 --- Comment #4 from Eyal Rozenberg --- (In reply to Myriam Schweingruber from comment #3) > I guessed as much. It's still a build failure, albeit of the testing code. Aren't you supposed to change the component or mark it somehow instead of testing it? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 Eyal Rozenberg changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Eyal Rozenberg --- (In reply to Myriam Schweingruber from comment #1) > Did you try building with testing disabled? No, I used the default options. With testing disabled, the build concludes without errors. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409837] New: CMakeLists.txt doesn't check for presence of Embedded MariaDB
https://bugs.kde.org/show_bug.cgi?id=409837 Bug ID: 409837 Summary: CMakeLists.txt doesn't check for presence of Embedded MariaDB Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 SUMMARY I'm building v2.9.0 on Debian buster (well, actually, Devuan Beowulf, which is the same thing but with systemd yanked out). CMake'ing works, but during linking, I get this error: [ 61%] Linking CXX shared module ../../../../../lib/amarok_storage-mysqlestorage.so /usr/bin/ld: cannot find -lmariadbd collect2: error: ld returned 1 exit status indeed, I didn't have embedded MariaDB installed. When I installed the package for it, the error went away. So, CMake should have checked for this library's presence - and didn't; or alternatively, mistakenly thought it had located it. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] New: Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 Bug ID: 409836 Summary: Build failure: Undefined reference to setMountPointManager(MountPointManager*) Product: amarok Version: 2.9.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 SUMMARY I'm building v2.9.0 on Debian buster (well, actually, Devuan Beowulf, which is the same thing but with systemd yanked out). CMake'ing works, and compilation goes fine. But during linking, I get the following: /usr/bin/ld: CMakeFiles/testsqltrack.dir/TestSqlTrack.cpp.o: in function `TestSqlTrack::initTestCase()': /usr/local/src/amarok-2.9.0/tests/core-impl/collections/db/sql/TestSqlTrack.cpp:52: undefined reference to `Collections::DatabaseCollection::setMountPointManager(MountPointManager*)' collect2: error: ld returned 1 exit status make[2]: *** [tests/core-impl/collections/db/sql/CMakeFiles/testsqltrack.dir/build.make:136: tests/testsqltrack] Error 1 make[1]: *** [CMakeFiles/Makefile2:3603: tests/core-impl/collections/db/sql/CMakeFiles/testsqltrack.dir/all] Error 2 and the same for a a few other targets. STEPS TO REPRODUCE 1. Install all relevant Debian packages for Amarok feature prerequisites 2. Run CMake on the v2.9.0 sources (downloaded today, 2019-07-14), with an out-of-source build directory 3. build SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux KDE Plasma Version: 5.54.0-1 KDE Frameworks Version: Not sure what number to put here. Qt Version: 5.11.3+dfsg1-1 ADDITIONAL INFORMATION Devuan Beowulf with no custom-built packages. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 403804] RequesT: Support KDE Framework v5.28, not just 5.31
https://bugs.kde.org/show_bug.cgi?id=403804 --- Comment #2 from Eyal Rozenberg --- (In reply to Michel Ludwig from comment #1) > Besides, frameworks 5.28 is already more than two years old. Stable distributions have a lot of code that is more than two years old; specifically, Debian. But - suit yourself. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 403804] New: RequesT: Support KDE Framework v5.28, not just 5.31
https://bugs.kde.org/show_bug.cgi?id=403804 Bug ID: 403804 Summary: RequesT: Support KDE Framework v5.28, not just 5.31 Product: kile Version: 2.9.92 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: eyal...@technion.ac.il Target Milestone: --- I'm trying to build Kile 3.0b2 (2.9.92) on a Devuan ASCII machine (it's essentially Debian Stretch). Now, Debian Stretch has version 5.28 of the KDE Framework, while KIle needs v5.31. I don't know what the exact differences are, but - if possible, can you get 2.9.92 to build with the prerequisites available on Debian? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 --- Comment #5 from Eyal Rozenberg --- Created attachment 115277 --> https://bugs.kde.org/attachment.cgi?id=115277=edit v2.9.0 console capture as problem manifests The contents of this file are what gets printed to the console (stdout + stderr) when running amarok v2.9.0, playing a file, with the bug manifesting shortly afterwards, i.e. playback continues but the GUI becomes unresonsive. I should also mention that in addition to the UI, other windows seem to get spawned which then disappear; not sure if that's related or not. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399097] Amarok fails to locate plugins after installation to non-default location, no useful feedback provided to user
https://bugs.kde.org/show_bug.cgi?id=399097 Eyal Rozenberg changed: What|Removed |Added Summary|Amarok fails to locate |Amarok fails to locate |plugins after installation, |plugins after installation |no useful feedback provided |to non-default location, no |to user |useful feedback provided to ||user -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399097] Amarok fails to locate plugins after installation, no useful feedback provided to user
https://bugs.kde.org/show_bug.cgi?id=399097 --- Comment #1 from Eyal Rozenberg --- The plugins are found if I set the environment variable KDEDIRS="/usr/local:/usr" but I only found this out by talking to a developer on IRC. I believe Amarok could be expected to use its CMake-configured installation as a KDEDIRS entry; and this would have avoided the issue manifesting. Regardless, had the information I suggested been reported to the user, it would have been almost trivial to resolve the problem with no developers/IRC channel member help. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 Eyal Rozenberg changed: What|Removed |Added Resolution|UNMAINTAINED|--- Version|unspecified |2.9.0 Status|NEEDSINFO |REPORTED --- Comment #4 from Eyal Rozenberg --- Ok, so, I have reproduced the bug with v2.9.0. But - now I don't get the repeating QLContext error messages. In case it matters - I set KDEDIRS="/usr/local:/usr" to get v2.9.0 to find its plugins and agree to run. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399097] New: Amarok fails to locate plugins after installation, no useful feedback provided to user
https://bugs.kde.org/show_bug.cgi?id=399097 Bug ID: 399097 Summary: Amarok fails to locate plugins after installation, no useful feedback provided to user Product: amarok Version: 2.9.0 Platform: Other OS: All Status: REPORTED Severity: major Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 I've just built Amarok v2.9.0 on my (Debian Stretch / Devuan ASCII) system, installing it under `/usr/local`. I've followed the instructions on the Amarok website, and installation was successful. But - when I start the app up, I get a message telling me: "Amarok could not find any plugins. The indicates an installation problem." First, this should just not happen. If the installation succeeded, the app should come up. Otherwise, `make install` should have failed, and produced some message regarding what's missing. Alternatively, CMake should have checked for whatever it is amarok needs (plugins etc.) or determined the directories where those resources are found - or alternatively, fail to configure the build. Even if the latter has not been done, the error message should tell the user: * Which directories were searched for plugins * What specific plugins are required which were not found * Where the user should the missing necessary plugins * How / where to get those plug-ins, or source code for building them -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399052] Compilation fails on __attribute__((fallthrough))
https://bugs.kde.org/show_bug.cgi?id=399052 Eyal Rozenberg changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 --- Comment #3 from Eyal Rozenberg --- (In reply to Myriam Schweingruber from comment #2) Well, I doubt things are different with 2.9.0 (unless you've worked on something related to this issue). Regardless, I'll update this issue right after I manage to _build_ 2.9.0 (see bug 399052). -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399052] New: Compilation fails on __attribute__((fallthrough))
https://bugs.kde.org/show_bug.cgi?id=399052 Bug ID: 399052 Summary: Compilation fails on __attribute__((fallthrough)) Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 I'm trying to build Amarok 2.9.0 on a Debian Stretch machine (well, Devuan ASCII, but it's essentially the same), after having manually built and installed Googletest (inc. Google Mock) and neopomuk-core, which I couldn't obtained using distribution packages. CMake passes fine, with all optional packages located, but compilation fails: /usr/local/src/amarok-2.9.0/src/playlist/proxymodels/SortAlgorithms.cpp: In member function ‘bool Playlist::multilevelLessThan::operator()(const QAbstractItemModel*, int, int) const’: /usr/local/src/amarok-2.9.0/src/playlist/proxymodels/SortAlgorithms.cpp:98:21: error: expected primary-expression before ‘__attribute__’ __attribute__ ((fallthrough)); ^ src/CMakeFiles/amaroklib.dir/build.make:2712: recipe for target 'src/CMakeFiles/amaroklib.dir/playlist/proxymodels/SortAlgorithms.cpp.o' failed If I comment-out the attribute, compilation (of that file at least) succeeds. I'm using the following compiler: g++ (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 Eyal Rozenberg changed: What|Removed |Added Version|2.9.0 |unspecified Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 --- Comment #1 from Eyal Rozenberg --- I should also mention that I experience other issues, probably related to the same system setup, on my system. Perhaps the most significant example (and the only one I can remember and reproduce right now) is that Cinnamon only manages to start up in Fallback mode, and in regular startup it crashes. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 399037] New: Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang
https://bugs.kde.org/show_bug.cgi?id=399037 Bug ID: 399037 Summary: Repeated "QGLContext::makeCurrent(): Cannot make invalid context current” and hang Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 SUMMARY I've using Amarok 2.8.0 on Devuan 2 as well as on Linux Mint 18.3. My hardware and driver setup is valid, but atypical: I use on-board graphics for X, but also use an nVIDIA graphics card (with its drivers loaded) for computation. This gives me some OpenGL issues in certain cases, and specifically with Amarok: When I run it, I get the repeating error message: QGLContext::makeCurrent(): Cannot make invalid context current and the app hangs after a bit of use. Sometimes more, sometimes less. STEPS TO REPRODUCE 1. Get a machine with on-board graphics and an nVIDIA graphics card 2. Install a recent version of CUDA (includingn an nVIDIA kernel driver). 3. Configure your X server is configured to use the on-board graphics, not the nVIDIA card. 4. Make sure you can actually run some of the CUDA samples or at least that `nvidia-smi` gives you information about your card - while running X. 5. Install a non-KDE desktop environment, e.g. Cinnamon 6. Run amarok 7. Add some audio files to a playlist and start playing EXPECTED RESULT No repeating error message, app runs normally, music plays. ACTUAL RESULT After a short while, the amarok UI is no longer responsive (although the music continues playing); the app cannot be shut down except with a signal. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The card is a GeForce 650 Ti Boost, although that shouldn't matter. The CPU is an Intel x86_64 4-core chip. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392247] New: Structure tree construction does not ignore sectioning within comment environment
https://bugs.kde.org/show_bug.cgi?id=392247
Bug ID: 392247
Summary: Structure tree construction does not ignore sectioning
within comment environment
Product: kile
Version: unspecified
Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: michel.lud...@kdemail.net
Reporter: eyal...@technion.ac.il
Target Milestone: ---
I'm using Kile 2.1.3 (on Mint 18.3).
After everything else in my document (report class), I have the following code:
\begin{comment}
\appendix
\chapter*{Appendix}
\section*{Frobnicate the bar}
Bunch of text here, etc. etc.
\endcomment}
... and this shows up as part of the document structure tree, which it really
shouldn't - especially seeing how the comment environment is identified and its
contents is grayed-out.
This bug seems very related to bug 63121, which was about line comments (text
after the % symbol). However, that one was resolved 15 years ago. In fact, if I
add line comments within the comment environment, the appendix and the section
disappear from the structure tree; so it really looks like they're treated like
a normal part of the document.
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 391422] Need to be able to search only non-commented code
https://bugs.kde.org/show_bug.cgi?id=391422 Eyal Rozenberg <eyal...@technion.ac.il> changed: What|Removed |Added OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 391422] New: Need to be able to search only non-commented code
https://bugs.kde.org/show_bug.cgi?id=391422
Bug ID: 391422
Summary: Need to be able to search only non-commented code
Product: kile
Version: 2.1.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: editor
Assignee: michel.lud...@kdemail.net
Reporter: eyal...@technion.ac.il
Target Milestone: ---
Kile is able to distinguish code (and text) that's commented, whether with a
percentage sign or within a {comment} environment. This functionality should
also be usable when searching, to avoid matches which are commented - if the
user has marked a checkbox saying s/he wants this.
This is related to bug 377334 (Ignore folded fragments of code when doing
search), but I believe should be of higher priority.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 370400] New: Automatically switch profile on relevant events
https://bugs.kde.org/show_bug.cgi?id=370400 Bug ID: 370400 Summary: Automatically switch profile on relevant events Product: konsole Version: 16.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: eyal...@technion.ac.il I often wish I could change the profile when logging in or out of various remote machines (to better remind me I'm not working locally); right now, I have to switch profiles manually, but, really, Konsole is aware of hostname changes. So one could associate these changes with a profile switch. Also, profiles could switch based on any of the other 'monitored' values used in tab titles: Program name, user name, window title set by shell, hostname, current directory and maybe others - for example, using per-profile regexps for matching these values. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] New: Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 Bug ID: 370397 Summary: Support coloring/tinting of tabs Product: konsole Version: 16.08.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: eyal...@technion.ac.il The tabs on the tab bar should support being colored, or rather tinted relative to the basic UI tab color. At a minimum this will be part of the profile settings, like the profile icon setting. Beyond that, it would be nice to allow tab tint based on various criteria such as whether it's a remote host or not, or whether there's been new output since the tab was last viewed etc. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
