On 8/7/06, Clint Adams [EMAIL PROTECTED] wrote:
Certainly. Attached (probably more than is relevant).
BTW, this is rake 0.7.1-1 from unstable and, as can be probably guessed,
the Rakefile comes from rails.
See if this fixes it.
Not quite. It presents you with the correct completions, but
On Sun, 6 Aug 2006 23:21:30 -0400, Clint Adams wrote:
Certainly. Attached (probably more than is relevant).
BTW, this is rake 0.7.1-1 from unstable and, as can be probably guessed,
the Rakefile comes from rails.
See if this fixes it.
Not fully. Things get better, though.
The proposals
On Sat, 5 Aug 2006 21:32:17 -0400, Clint Adams wrote:
For rake tasks named like eg. db:fixtures:load the completion treats only
the 'db' at the beginning as the string to complete and prepends the rest
of the task
name (ie. 'fixtures:load') to its description.
Can you send the
Certainly. Attached (probably more than is relevant).
BTW, this is rake 0.7.1-1 from unstable and, as can be probably guessed,
the Rakefile comes from rails.
See if this fixes it.
Index: Completion/Unix/Command/_rake
===
RCS
For rake tasks named like eg. db:fixtures:load the completion treats only
the 'db' at the beginning as the string to complete and prepends the rest of
the task
name (ie. 'fixtures:load') to its description.
Can you send the relevant output from `rake -sT` for that task?
--
To UNSUBSCRIBE,
Package: zsh
Version: 4.3.2-14
Severity: normal
For rake tasks named like eg. db:fixtures:load the completion treats only
the 'db' at the beginning as the string to complete and prepends the rest of
the task
name (ie. 'fixtures:load') to its description.
--
Michał Politowski
Talking has been
6 matches
Mail list logo
