* branch_state: no branch => on review
Comment:
Branch: 3375_hardlink_highlight
changeset:aa8033cae4d50555c1a851e1df1b5d67a7fe25fa
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:3>
Midnight Commander <https://midnight-commander.org>
Midnight Development Center
* owner: => andrew_b
* status: new => accepted
* milestone: Future Releases => 4.8.27
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:2>
* votes: => andrew_b
* branch_state: on review => approved
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:4>
* status: accepted => testing
* votes: andrew_b => committed-master
* resolution: => fixed
* branch_state: approved => merged
Comment:
Merged to master: [1a1c6cc27817b9d37ce8e057e0d594184f635d73].
{{{
git log --pretty=oneline 83d496680..1a1c6cc27
}}}
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:5>
* status: testing => closed
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:6>
* cc: onlyjob@… (added)
Comment:
I always thought it was a useful feature - to highlight hardlinks
differently...
Now, how can I see if file have any hardlinks or if I just deleted the
last hardlink?
Perhaps coloring was inconsistent but I've got accustomed to this
bug-o-feature over the years.
Would it be possible to visually mark hardlinked files somehow, so they'd
stand out among ordinary files?
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:7>
Comment (by zaytsev):
Maybe it would make sense to mark those files with a special character,
like `*` for the executable files? For example with `+` ? It think that
this would be much better than an implicit inconsistent highlighting. What
do you think? Care to create a ticket?
--
Ticket URL: <http://www.midnight-commander.org/ticket/3375#comment:8>