On 04/05/10 02:01, Michael Lachmann wrote:
>
> On 5 Apr 2010, at 1:04, David Frascone wrote:
>
>> That's two seperate problems:
>>
>> 1) not properly quoting the URL so that the hash is interpreted as a
>> comment
>
> That is not actually the only problem here. The problem is that
> open 'file:/som
On 5 Apr 2010, at 1:04, David Frascone wrote:
> That's two seperate problems:
>
> 1) not properly quoting the URL so that the hash is interpreted as a
> comment
That is not actually the only problem here. The problem is that
open 'file:/somewhere/commands.html#complete'
complains that there is
That's two seperate problems:
1) not properly quoting the URL so that the hash is interpreted as a
comment
2) bad installation confused about the location of the help files.
-Dave
Sent from my iPhone
On Apr 4, 2010, at 5:05 PM, Philip Ganchev
wrote:
> The problem is more general. For exa
The problem is more general. For example, on Linux where "help" is
configured to use w3m:
~> help complete
w3m: Can't load file:///usr/share/doc/fish/builtins.html#complete.
~> ls /usr/share/doc/fish/builtins.html
ls: cannot access /usr/share/doc/fish/builtins.html: No such file or directory
~> w3
On my machine, calling help only opens the main help page, and does
not go to the specific page.
So:
help complete
open the help page commands.html, instead of commands.html#complete
(I have BROWSER set to "open")
To fix that, I wrote a little applescript:
---
#!/usr/bin/osascript
on run argv
