Ticket #2920 (new enhancement)

Opened 12 years ago

Last modified 7 years ago

Better skin files

Reported by: iwfmp Owned by:
Priority: major Milestone: Future Releases
Component: documentation Version: master
Keywords: Cc: egmont@…
Blocked By: Blocking:
Branch state: no branch Votes for changeset:


I forked and improved a theme called "solarized".
I made a few improvements:

  1. Adding comments on each line.
  2. Collecting all variables I could find.

I shouldn't explain why this is necessary -
The documentation at the moment is pure garbage,
and it took me a while to collect all entries,
and a while more to understand what each entry does.

It is still incomplete, and I hope some could help with the stuff I, personally, don't use (like the editor or viewer), or refer to the TODO's there to help explain entries I couldn't find or understand.

You are free to view it here:

Change History

comment:1 Changed 11 years ago by egmont

  • Cc egmont@… added

I agree that mc lacks a good documentation on the entries of skin files. It's always been bugging me, I guess I'll just create one, based on your work and my findings.

I also think that it'd be cool to have a Solarized skin officially shipped by mc. I'm not sure you intend to get your skin accepted mainstream. I think it would be cool if you did, but of course it requires some more work then to fully finish it.

Be aware that legacy terminals supported 16 foreground and 8 background colors, only indices 0-7 (in the column "16" under Values on Solarized homepage http://ethanschoonover.com/solarized) are valid for background. TERM=xterm describes such a terminal. If you do use any of the 8-15 colors as background (and you do) then running with TERM=xterm results in a different look than with TERM=xterm-256color, e.g. violet becomes magenta. This is probably undesired. See #3050. (I'm not sure the author of Solarized thought about this. All the screenshots there use such colors as background, hence likely don't work if obeying the "xterm" terminfo instructions, as ncurses/slang does.) One possible approach is to force 256 color support in the skin.

Checking the description and the screenshots on the Solarized homepage I have a feeling that the spirit of this color scheme would require not mixing light and dark backgrounds, but instead have two versions (one with light background and one with dark background) which only differ in the four baseN and base0N pairs being swapped.

comment:2 Changed 8 years ago by andrew_b

  • Milestone changed from Documentation to Future Releases

comment:3 Changed 7 years ago by egmont

Just for the record, here are some of the less trivial colors, especially when not clear (to me) from the comments in iwfmp's solarized skin or when the name is extremely misleading:

[core] -> inputmark, commandlinemark; [editor] -> editmarked: Highlight text with mouse, or use Shift + Left or Right arrow.

[core] -> gauge: Progress bar.

[core] -> reverse: The path at the top of the active panel.

[statusbar]: Top row in mcview and mcedit.

[editor] -> editbold: Search result.

[editor] -> editlinestate: Enable line numbers with Alt+N.

[editor] -> editrightmargin: Enable editor_show_right_margin in the config file.

[editor] -> editbg, editframe*: Open multiple files, F9 -> Window -> Toggle fullscreen (or click on the left symbol in the upper right corner), drag them around. editbg is the unused area.

[editor] -> bookmark: Search -> Toggle bookmark, or Alt+K.

[editor] -> bookmarkfound: F7 -> Find all.

[viewer] -> viewbold, viewunderline: used with *roff files (manual pages).

[diffviewer]: See #3759.

See also #3159.

Note: See TracTickets for help on using tickets.