Ticket #3191 (new enhancement)
Clarify priority/order of mc.ext conflicting entries.
Reported by: | gavenkoa | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Future Releases |
Component: | mc-core | Version: | master |
Keywords: | mc.ext | Cc: | gavenkoa |
Blocked By: | Blocking: | ||
Branch state: | no branch | Votes for changeset: |
Description
I already report related bugs #2773 and #2772 but now want that team make clear statement in docs (guaranty) about priority of mc.ext conflicting entries.
I use system (Debian) mc.ext with personal tweaks:
$ cat /etc/mc/mc.ext $skel/.config/mc/mc.ext > ~/.config/mc/mc.ext
After experimenting I found that last entry have priority over upper.
But there are no any guaranties in docs or MC Trac.
About same keyword:
shell/.doc Open=echo SHELL 111 shell/.doc Open=echo SHELL 222
or about different keywords:
shell/.doc Open=echo SHELL regex/\.[dD][oO][cC]$ Open=echo REGEX
or about include priority:
include/funny Open=echo FUNNY pre 111 shell/.fun Include=funny include/funny Open=echo FUNNY post 222 include/funny Open=echo FUNNY post 333
or about merge of options:
shell/.doc Open=echo OPEN shell/.doc View=echo VIEW
Change History
Note: See
TracTickets for help on using
tickets.
Also interesting case:
and: