Ticket #3191 (closed enhancement: fixed)
Clarify priority/order of mc.ext conflicting entries.
Reported by: | gavenkoa | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 4.8.29 |
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
comment:3 Changed 2 years ago by andrew_b
- Status changed from new to closed
- Resolution set to fixed
- Milestone changed from Future Releases to 4.8.29
Done in [d9eeec9a5a74cae570992e9665eea7dd5ae7a98b].
See the comments in mc.ext.ini:
Sections are processed from top to bottom, thus the order is important. If there are more than one sections with the same name in this file, the first section will be used.
If there are more than one keys with the same name in a section, the last key will be used.
comment:4 Changed 12 months ago by andrew_b
The comment above was fixed in [75577b66a726448e742966c3a833d3095e4fefb4].
Note: See
TracTickets for help on using
tickets.
Also interesting case:
and: