https://bugs.kde.org/show_bug.cgi?id=421057
--- Comment #11 from Nikita Sirgienko <warqu...@gmail.com> --- (In reply to avlas from comment #9) > (In reply to Nikita Sirgienko from comment #8) > > (In reply to avlas from comment #5) > > > I guess this issue could be rephrase as follows: > > > > > > - Use non-monospace system font for text that is not actually code: raw > > > text > > > input and markdown > > > > > > - Display proper font name in the toolbar, i.e., system's monospace > > > default > > > font when using code input and system's non-monospace default font when > > > using regular text and markdown. Then the user can change those if wanted > > Yes, you right. Cantor shouldn't use monospace on text and markdown entries. > > Also, default value of font changer should be fixed too. But actually, this > > toolbar should work only in text entries. For all another entries there is > > "Right Click Menu -> Font -> Select". > > I see. Thanks for letting me know. > > One more thing I just realized. Is it possible to edit Markdown entries? It > seems I cannot modify those, but maybe I'm missing how to do this properly In what sense edit? Markdown entry have two state "editing" and "rendered". You can edit the entry with "editing" state but not in "rendered". Evaluation change state from "editing" to "rendered" (and do render), but double click on the markdown entry change it from "rendered" to "editing". So if you want to change already executed Markdown Entry, you just need double click it. -- You are receiving this mail because: You are watching all bug changes.
