[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #24 from avlas --- (In reply to Laurent Montel from comment #23) > > Sorry, I think I didn't explain myself well. I was not talking here now > > about the conversion from markdown to html, but about highlighting the email > > body in the composer while writing (if/when the markdown button is > > activated). In that case, it would be great to see how markdown keywords > > written in plain text get automatically highlighted. This would help writing > > markdown emails, e.g. to better structure the email or more easily visualize > > markdown typos. > > Ah ok. I don't know if it's possible but indeed I can look at it. Great, thanks -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #23 from Laurent Montel --- (In reply to avlas from comment #22) > (In reply to Laurent Montel from comment #21) > > (In reply to avlas from comment #20) > > > (In reply to Laurent Montel from comment #18) > > > > Created attachment 119461 [details] > > > > Screenshot > > > > > > I had some ideas for further enhancement after seeing your screenshot (as > > > well as this one http://25.io/mou/img/1...@2x.png): > > > > > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > > > technology as well to ease writing emails in markdown format, so it gets > > > automatically enabled when the markdown button in the composer is > > > activated. > > > > KSyntaxHighlighting highlights only text, it can create a html code but not > > for converting > > markdown to html. > > Sorry, I think I didn't explain myself well. I was not talking here now > about the conversion from markdown to html, but about highlighting the email > body in the composer while writing (if/when the markdown button is > activated). In that case, it would be great to see how markdown keywords > written in plain text get automatically highlighted. This would help writing > markdown emails, e.g. to better structure the email or more easily visualize > markdown typos. Ah ok. I don't know if it's possible but indeed I can look at it. > > > > 2) It would be so great to have a live preview (as shown in the link > > > above; > > > please note that Kate has already something similar to this) instead of a > > > pop-up window. > > > > We can't do it as composer is a "QTextEdit" and we need a html viewer/editor > > for showing > > mardown result. QTextEdit is too limited for html. > > I see. That's a pity, such a feature would probably attract users, > especially KDE users using markdown-here in other email client applications > or in the browser. yep but in thunderbird they use a html editor directly... It's not possible in Qt. > > I know there is the option but never tried using an external editor for > writing emails. I assume this would not be an option for writing emails in > markdown either, right? Saying because perhaps one could use Kate for this... > > > > 3) It would be nice if there could be an option to remember the status of > > > the Markdown button in the composer. > > > > We can do it. I will look at it. > > Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #22 from avlas --- (In reply to Laurent Montel from comment #21) > (In reply to avlas from comment #20) > > (In reply to Laurent Montel from comment #18) > > > Created attachment 119461 [details] > > > Screenshot > > > > I had some ideas for further enhancement after seeing your screenshot (as > > well as this one http://25.io/mou/img/1...@2x.png): > > > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > > technology as well to ease writing emails in markdown format, so it gets > > automatically enabled when the markdown button in the composer is activated. > > KSyntaxHighlighting highlights only text, it can create a html code but not > for converting > markdown to html. Sorry, I think I didn't explain myself well. I was not talking here now about the conversion from markdown to html, but about highlighting the email body in the composer while writing (if/when the markdown button is activated). In that case, it would be great to see how markdown keywords written in plain text get automatically highlighted. This would help writing markdown emails, e.g. to better structure the email or more easily visualize markdown typos. > > 2) It would be so great to have a live preview (as shown in the link above; > > please note that Kate has already something similar to this) instead of a > > pop-up window. > > We can't do it as composer is a "QTextEdit" and we need a html viewer/editor > for showing > mardown result. QTextEdit is too limited for html. I see. That's a pity, such a feature would probably attract users, especially KDE users using markdown-here in other email client applications or in the browser. I know there is the option but never tried using an external editor for writing emails. I assume this would not be an option for writing emails in markdown either, right? Saying because perhaps one could use Kate for this... > > 3) It would be nice if there could be an option to remember the status of > > the Markdown button in the composer. > > We can do it. I will look at it. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #21 from Laurent Montel --- (In reply to avlas from comment #20) > (In reply to Laurent Montel from comment #18) > > Created attachment 119461 [details] > > Screenshot > > I had some ideas for further enhancement after seeing your screenshot (as > well as this one http://25.io/mou/img/1...@2x.png): > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > technology as well to ease writing emails in markdown format, so it gets > automatically enabled when the markdown button in the composer is activated. KSyntaxHighlighting highlights only text, it can create a html code but not for converting markdown to html. > 2) It would be so great to have a live preview (as shown in the link above; > please note that Kate has already something similar to this) instead of a > pop-up window. We can't do it as composer is a "QTextEdit" and we need a html viewer/editor for showing mardown result. QTextEdit is too limited for html. > > 3) It would be nice if there could be an option to remember the status of > the Markdown button in the composer. We can do it. I will look at it. > > Please let me know if these ideas make sense and if you would like me to > open new bug reports for them, especially points 2 and 3 above, which are > not about highlighting. > > I can easily foresee myself in the near future writing all my emails in > markdown format instead of plain text :) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #20 from avlas --- (In reply to Laurent Montel from comment #18) > Created attachment 119461 [details] > Screenshot I had some ideas for further enhancement after seeing your screenshot (as well as this one http://25.io/mou/img/1...@2x.png): 1) It would be great if Kmail composer would use KSyntaxHighlighting technology as well to ease writing emails in markdown format, so it gets automatically enabled when the markdown button in the composer is activated. 2) It would be so great to have a live preview (as shown in the link above; please note that Kate has already something similar to this) instead of a pop-up window. 3) It would be nice if there could be an option to remember the status of the Markdown button in the composer. Please let me know if these ideas make sense and if you would like me to open new bug reports for them, especially points 2 and 3 above, which are not about highlighting. I can easily foresee myself in the near future writing all my emails in markdown format instead of plain text :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders
https://bugs.kde.org/show_bug.cgi?id=284172 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 292285] Cannot specify IMAP server directory
https://bugs.kde.org/show_bug.cgi?id=292285 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #19 from avlas --- (In reply to Laurent Montel from comment #18) > Created attachment 119461 [details] > Screenshot Neat! (thank you) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #18 from Laurent Montel --- Created attachment 119461 --> https://bugs.kde.org/attachment.cgi?id=119461=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #17 from avlas --- (In reply to Laurent Montel from comment #16) > Now we can hightlight block. > I need to fix some little bugs but it's good now :) Excellent! [ If you'd have a chance and it's not too much trouble, please attach a screenshot of an example. I'd love to see it in action :) ] -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 Laurent Montel changed: What|Removed |Added Version Fixed In||5.12.0 Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kde ||pim-addons/c162085500515502 ||8cb1e88a739abe9adf066353 Resolution|--- |FIXED --- Comment #15 from Laurent Montel --- Git commit c1620855005155028cb1e88a739abe9adf066353 by Laurent Montel. Committed on 17/04/2019 at 11:43. Pushed by mlaurent into branch 'master'. Fix Bug 406333 - Markdown addon: support syntax highlighting FIXED-IN: 5.12.0 M +2-1kmail/editorconvertertextplugins/markdown/CMakeLists.txt M +5-5 kmail/editorconvertertextplugins/markdown/autotests/CMakeLists.txt M +23 -43 kmail/editorconvertertextplugins/markdown/markdownconverter.cpp A +87 -0 kmail/editorconvertertextplugins/markdown/markdownhighlighter.cpp [License: GPL (v2+)] A +42 -0kmail/editorconvertertextplugins/markdown/markdownhighlighter.h [License: GPL (v2+)] M +2-2kmail/editorconvertertextplugins/markdown/tests/CMakeLists.txt https://commits.kde.org/kdepim-addons/c1620855005155028cb1e88a739abe9adf066353 -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #16 from Laurent Montel --- Now we can hightlight block. I need to fix some little bugs but it's good now :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406623] New: akonadi maildir resource crash cannot be reported via DrKonqi
https://bugs.kde.org/show_bug.cgi?id=406623 Bug ID: 406623 Summary: akonadi maildir resource crash cannot be reported via DrKonqi Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: christiande...@web.de Target Milestone: --- SUMMARY If the akondadi maildir resource crashes, DrKonqi is started. However you can only get the backtrace but are not able to report the crash via DrKonqi. STEPS TO REPRODUCE 1. Let akonadi maildir resource crash 2. DrKonqi starts 3. Button to report the bug is gray and the text above says "you cannot report the bug as the application akonadi maildir resource has no address to report the bug. (translated back from German) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Akonadi 19.03.80 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406621] New: akonadi maildir resource sometimes crashes when changing folders
https://bugs.kde.org/show_bug.cgi?id=406621 Bug ID: 406621 Summary: akonadi maildir resource sometimes crashes when changing folders Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: christiande...@web.de Target Milestone: --- Sometimes the akonadi maildir resource crashes. As far as I have observed it, it only happens when I change to mail in another folder. However it does not always happen and so far I was not able to find exact steps to reproduce it. However it happens quite regularly for me. This is using the th 19.03.80 version of KDE applications. Backtrace is attached Linux/KDE Plasma: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Akonadi 19.03.80 ADDITIONAL INFORMATION Application: akonadi_maildir_resource (akonadi_maildir_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb12be1f900 (LWP 17409))] Thread 4 (Thread 0x7fb1132f0700 (LWP 17462)): [KCrash Handler] #6 0x7fb12880c0e0 in raise () from /lib64/libc.so.6 #7 0x7fb12880d6c1 in abort () from /lib64/libc.so.6 #8 0x7fb128e3be83 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7fb128e41dd8 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7fb128e41e23 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7fb1291c193b in qTerminate () at global/qglobal.cpp:3192 #12 0x7fb1291e596b in QThreadPrivate::start (arg=0x55e74a3d8c80) at thread/qthread_unix.cpp:373 #13 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #14 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb113af1700 (LWP 17459)): #0 0x7fb1288c407b in poll () from /lib64/libc.so.6 #1 0x7fb1243ca129 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb1243ca23c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a3bc6a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fb113af0c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb1291e403a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fb12a103d55 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fb1291e57e2 in QThreadPrivate::start (arg=0x7fb12a37bd80) at thread/qthread_unix.cpp:361 #8 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb118b94700 (LWP 17434)): #0 0x7fb1288c407b in poll () from /lib64/libc.so.6 #1 0x7fb11f512387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb11f513fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb11b9897d8 in QXcbEventQueue::run (this=0x55e74a348300) at qxcbeventqueue.cpp:228 #4 0x7fb1291e57e2 in QThreadPrivate::start (arg=0x55e74a348300) at thread/qthread_unix.cpp:361 #5 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb1288ce81f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb12be1f900 (LWP 17409)): #0 0x7fb126214c34 in pthread_getspecific () from /lib64/libpthread.so.0 #1 0x7fb1243f1dd0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb1243ca22d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a327e80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fffb7ae3e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb1293c5cb0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1363 #6 0x7fb12b366b4d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libKF5AkonadiAgentBase.so.5 #7 0x55e748e20271 in ?? () #8 0x7fb1287f6f4a in __libc_start_main () from /lib64/libc.so.6 #9 0x55e748e200fa in ?? () [Inferior 1 (process 17409) detached] -- You are receiving this mail because: You are the assignee for the bug.
