Hello Martin,
Post by Martin SteerPost by Johannes WeiÃlPost by Martin SteerI notice that Esc doesn't close the command prompt, as both ^C and ^G do
(Esc does close the prompt in vim).
Hmm, it does close the command prompt for me (but after a short timeout,
just like in vim).
I can't reproduce this at will, but Esc sometimes won't clear command
text, and sometimes won't close the prompt.
That is strange, it should always clear and close the prompt. Of course
you have to wait the timeout period, otherwise it won't work. See below
for alternatives. Can you reproduce the behaviour and tell the name of
the system and terminal emulator you are using?
Post by Martin SteerAs an aside, is there any reason for the timeout? It's sometimes
irritating in vim, and irritating here as well. Esc's useful with
filters, say if you start to enter one and decide to clear it. (I'm so
used to hitting Esc that it's always the first thing I try.)
Esc is used for escape sequences [1], that is the reason for the
timeout. This is why (I guess) most console users don't use it to clear
the prompt. Ctrl-C is an option, or Ctrl-U.
[1] http://en.wikipedia.org/wiki/Escape_sequence
Post by Martin SteerPost by Johannes WeiÃlPost by Martin SteerIn the Settings view, the functions of ^C and 'I' are badly (or
wrongly) described, I guess because of the way they're generated. The
descriptions reoccur in the manual.
What do you mean? The settings view does not contain a description of
the commands, but a literal mapping (key <-> command), which is accurate
but maybe not very descriptive. They could of course be explained in the
manual.
Should be explained in the manual, if not obvious.
Can you write a patch so it is clearer what you mean?
Post by Martin SteerWell, the binding on ^C is somewhat odd, given that the configurable
default is a note to the user that the key won't quit cmus. But I see
that it allows me to remove a message I may get tired of.
Ctrl-C closes the prompt (think of it as a fast Esc) when in
command-line mode. The other key binding is a help for users, because
Ctrl-C is often used to quit command-line programs. If you see this
message when you are editing the prompt (after pressing Ctrl-C), this is
a bug. In that case, can you mail what system and terminal emulator you
are using?
Post by Martin SteerPost by Johannes WeiÃlPost by Martin SteerThe error message for 'I' (in the screens where it's unsupported)
would be better if shortened to "Echo is supported only in views 1-4".
Hmm, but echo is supported in views other than 1-4, only the '{}'
substitution doesn't work, so the error message seems to be correct.
Not from the point of view of the user. In the Browser view, for
example, nothing gets echoed, as far as I can tell. I'm no wiser after
consulting the manual.
Try ":echo foo" in browser view, it should work. Only if '{}' appears,
e.g. ":echo foo {}", it doesn't work (because no track is selected).
Post by Martin SteerAre you interested in genealogy? I think a cmus-like interface would be
great for displaying family data. Filtering's useful there too.
Hmm, I'm not specifically interested (maybe others?). But for genealogy
a graphical output (with a tree that supports more than two levels ;-))
would be better suited. Cmus interface isn't 100% separated from the
backend, so it is not easy to use it for other applications.
Johannes