THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1201 - [PATCH] menu: allow markup in menu entries
User who did this - Enrico Scholz (ensc)
----------
I use a function to to do extended operations (e.g. calling :set_wrap() or
:set_ellipsize() functions) on the label or to replace it with an user defined
widget. This is the most flexible way.
Another (more extensive) way to solve this will be the definition of custom
datatypes; e.g. as
function util.markup_plain(text)
return { MARKUP_PLAIN, text }
end
function util.markup_hotkey(text, key)
return { MARKUP_HOTKEY, text, key }
end
and checking for these types (--> if type(text) == "table" and text[1] ==
MARKUP_PLAIN ...). But introducing another level of escaping as proposed in
FS#750 is error prone and will cause unexpected results for corner cases.
When you want, I can provide a patch which renames the 'text' variable to
something like 'content'.
----------
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1201#comment3777
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
