#49 Mechanism to group Highlight Styles

open
nobody
None
5
2003-08-26
2003-08-26
Wally Crooze
No

It would be nice to have a way of grouping highlight
styles. This would allow having different highlight
styles for different jobs, but not obfuscate the
highlight styles for all languages.

Grouping should be separate from Language Mode, but a
Language Mode would expect to select a Style Group,
with the default one being "Structured Languages" or
"Programmatical Languages".

This way I could have different Style Groups for
Programs, Compiler Output and Log files...

Discussion

  • Wally Crooze
    Wally Crooze
    2004-08-20

    Logged In: YES
    user_id=530199

    Suggestions on how to implement this woud be nice?!

     
  • Thorsten Haude
    Thorsten Haude
    2004-08-20

    Logged In: YES
    user_id=119143

    Would more styles do the trick? I always found the number of
    styles very limited. Often I cannot find anything matching
    and simply go for color.

     
  • Wally Crooze
    Wally Crooze
    2004-08-24

    Logged In: YES
    user_id=530199

    The problem is that I define styles depending on what they
    are to achieve. I am finding that with so many styles that
    the list is too long and is difficult to find what I'm
    looking for.

    On 5.5RC1 for Linux I can't see all the styles to select in
    the "Syntax Highlighting Patterns" dialog. Adding scroll
    arrows to these menus would be a start... but that isn't
    what I'm after either.

     
  • Thorsten Haude
    Thorsten Haude
    2004-08-24

    Logged In: YES
    user_id=119143

    I never noticed the limited space for styles. I guess more
    styles are out of the question until there is a better
    widget for them.

    Do you have an example for the original problem? What are
    you trying to achieve?

     
  • Wally Crooze
    Wally Crooze
    2004-08-24

    Logged In: YES
    user_id=530199

    (Apart from world domination) I would like to define
    separate, even overlapping in some cases, styles depending
    on the usage. An example would be that structured
    programming languages, such as C, Pascal, etc all have
    "Storage Type"s, "Function"s and more.

    These are what normal usage would require... but there are
    other cases, such as viewing log files and technical
    documentation, where a separate style definitions would be
    nice... as these programatical styles don't make any real sense.

    I have logs which are generated by a multi-threaded
    application... and so I create a separate style to match
    each thread for easier use. Also, an output level helps to
    attract attention, such as ERROR, WARNING or just a COMMENT.
    A lot of the output can be broken down further to highlight
    application specific information.

    By the time I have all these styles it becomes almost
    impossible to find the relevant one and feel that a "Style
    Group" specification would make it easy to locate
    appropriate styles. These "Style Group"s should be able to
    be created, modified and deleted as with "Languages Mode"s.
    A "Language Mode" then would have a "Style Group" specified
    and then Patterns would have the style selected from that group.