It seems, from the previous posts, that we should not hold our breath 
waiting for rich text in Leo.

Now the question is: how to make the most of Leo's current features in 
order to approximate a rich text experience? 
I am asking this question from the perspective of someone who would use Leo 
mostly as a PIM (storing data, reorganizing it, writing research based on 
that data). For me the biggest advantages of rich text, in this context, 
would have been: text colorization, text highlighting, different fonts, 
strikethrough. 
Of these, only text colorization seems to be currently supported by Leo's 
features, although it is not yet clear to me how exactly to achieve this; 
the easiest way, I guess, would be to select the text and then to press a 
user-defined key shortcut, corresponding to the specific color one want to 
give to that text. Is there any plugin already that allows me to do that?

As for something resembling the other features mentioned above, I am 
clueless on how it could be done. Different fonts in plain text? Well, then 
it would not be plain text any longer.
Text highlighting? Text color reverse (as used in old computing and still 
on some terminals)?
Is any of these doable within the current plain text-only framework? If so, 
are there plugins implementing them already?

I wouldn't want to use two panes, one with markdown code and the other for 
view rendering, as has been suggested. I am afraid it would make my 
workflow sort of schizophrenic.

I believe the simplest thing would be using only one pane, and implementing 
all the needed features (whatever can be done) within that pane.

As for strikethrough, a bizarre idea came to my mind: if we really cannot 
implement it via rich text, could we use a font that has both a letter and 
its strikethroughed equivalent. This way, we could select some text, and 
format it with strikethrough; each character would be substituted with its 
strikethroughed equivalent. It's just a bizarre idea, which may not work. 
Please comment.

What other solutions would you propose to implement workarounds that at 
least approximate the desired features?

Any suggestions greatly appreciated.

Thanks

Dufriz

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to