Replies: 7 comments 45 replies
-
|
Hi @muellerto. The problem is simple: workspace colors are mainly used in the prompt, where we need to use |
Beta Was this translation helpful? Give feedback.
-
|
Should be fixed now. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the none-icons are gone. I had this indeed in every "terminal" I tried on Windows (mintty, alacritty, wt, hyper, ConEmu, DOS-prompt). OK, meanwhile I have `autocmd lines configured which make different color schemes for different workspaces. |
Beta Was this translation helpful? Give feedback.
-
|
I found some more. I deleted a file named t, then clifm makes such a display:
|
Beta Was this translation helpful? Give feedback.
-
|
Should be fixed now. |
Beta Was this translation helpful? Give feedback.
-
|
Works good! I have only the green checkmark. Think this is intended. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it is intended. It's part of the new Unicode interface. |
Beta Was this translation helpful? Give feedback.
-
|
Btw, we have a new columns arrangement algorithm: still not as good as ls(1), but much better than before nonetheless. It's still an experimental, and thereby hidden feature. Compile as follows to enable it: export CPPFLAGS="$CPPFLAGS -DTIGHT_COLUMNS"
makeGive it a try and let me know if something comes out. I think it's a pretty neat improvement. |
Beta Was this translation helpful? Give feedback.
-
|
Point 3 is good. I also thought about this. A list which is filtered for the cwd. So that the user can see what is relevant here on this place. |
Beta Was this translation helpful? Give feedback.
-
|
Removed the Btw, I added validation for both autocommand option names and values. |
Beta Was this translation helpful? Give feedback.
-
|
The autocommand prompt message includes now a description, which can be customized. Add these lines to your config file: # Inform about autocommand options set for the current directory
# Available values:
# false: Do not print any message.
# mini: Minimal message (no options details).
# short: Add a list of modified option names (without values).
# long: Like 'short', but adding values to each option (default).
;InformAutocmd=long |
Beta Was this translation helpful? Give feedback.
-
|
Yeah! Something else: I tried to add a global autocmd line in my config specifying a sort order for some directories. But I failed. I have on my disk several directories containing hundreds of log files and these directories are always named Log, so my general idea is
This seems to be allowed but it doesn't work. OK, the
But this all doesn't work. When I use the interactive |
Beta Was this translation helpful? Give feedback.
-
|
Both Take a look at the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
In my case lines like As I said the long view is a clifmrc defined autocmd based on the workspace. Interesting is that the sorting I defined one line below is not mentioned in the Autocmd message line. Also the short view is not sorted as expected. And I use an ordinary build with GIT sources from right now. |
Beta Was this translation helpful? Give feedback.
-
|
Quick reply:
I'll take a look at the rest of the stuff. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. I've modified the main logic of the autocommands function: all matching entries are executed, instead of just the first one. This should fix your issue. Btw, the prompt message for autocommands is disabled until I find a way to properly display options for multiple autocmd entries. The main thing is this: should we print a) separate messages for each matching autocmd (more intrusive, but clearer), or rather b) a single message summarizing the options set by all matching autocmds (less intrusive, less clear)? Another advantage of the first approach is that it would allow us to specify whether a given entry is temporal (i.e. set via the Forgot to mention: autocmds are evaluated from top to bottom, and this means that the more general a pattern or rule is, the more on top of the list should it be placed. For example, this: autocmd ~/Documents lv=0
autocmd @ws1 lv=1won't work, because the first rule is overridden by the second one, since both of them match the current directory. Instead, you want this: autocmd @ws1 lv=1
autocmd ~/Documents lv=0 |
Beta Was this translation helpful? Give feedback.
-
|
Now I got it! I had a misunderstanding in the meaning of OK, with that I can now lay sorting instructions on concrete paths pointing on my several Log directories. I have seven at the moment, dynamically changing from week to week with the number of branch specific working copies I have. But I can't make a general rule, once for all, also for future ones. Ah, update: a single * in the middle of a path works, |
Beta Was this translation helpful? Give feedback.
-
Good to know. However, there are still a few regressions (due to the new implementation) I need to work out. Please report whatever comes out. |
Beta Was this translation helpful? Give feedback.
-
|
Replaced glob(3) by fnmatch(3) when checking autocmds: it's faster and more flexible. Now you can match your autocmd */Log ...instead of autocmd ~/work/*/test_cfg/Log ...which is more specific. |
Beta Was this translation helpful? Give feedback.
-
|
Can you reproduce it? Haven't seen any realloc error. EDIT: Forget about it. Reproduced it. |
Beta Was this translation helpful? Give feedback.
-
|
Should be fixed now. |
Beta Was this translation helpful? Give feedback.
-
|
On my Windows machine it didn't happen this morning. Tried it several times, was always good. I have the original version from yesterday still on Linux. |
Beta Was this translation helpful? Give feedback.
-
|
So, I had it again yesterday on my Linux machine with now two days old binaries and it seemed to be reproducible. Now with actual binaries the problem is indeed gone :) |
Beta Was this translation helpful? Give feedback.
-
|
We can consider this issue solved then. Thanks @muellerto. |
Beta Was this translation helpful? Give feedback.
-
Question: What's this?
Why are they all always equal? And why do I suddenly get these icons when I use parameter
-E?The picture is from my Windows machine. On Linux I can use
-Ewithout getting this effect. What does this depend on?BTW: I searched for an explanation in the wiki and in the FAQ. Seems that a documentation of the screen in both view modes (short and long), it's elements and the settings the elements depend on is missing.
Beta Was this translation helpful? Give feedback.
All reactions