undefined method `point' for nil:NilClass

[exos]

Error:

[exos@Hexodica xiki]$ xiki ls
- tried to run: Ls.menu
- error: .construct_path couldn't construct the path - is this a well-formed tree?: undefined method `point' for nil:NilClass
- backtrace:
  ./lib/xiki/tree.rb:788:in `construct_path'
  ./lib/xiki/tree.rb:1714:in `path'
  /tmp/xiki/lib/xiki.rb:359:in `path'
  /tmp/xiki/lib/xiki.rb:355:in `trunk'
  ./lib/xiki/tree.rb:1686:in `file'
  /tmp/xiki/menu/ls.rb:16:in `menu'
  ./lib/xiki/code.rb:210:in `eval'
  ./lib/xiki/launcher.rb:936:in `invoke'
  ./lib/xiki/launcher.rb:152:in `add_menu'

Instaled from github (today) Some data:

[exos@Hexodica xiki]$ uname -a
Linux Hexodica 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[exos@Hexodica xiki]$ ruby --version
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

[jrichter]

I believe point is referring to point in emacs. I think this command is intended to be run from inside emacs. Try loading up emacs and typing: $ ls then double clicking on it, or pressing ctrl + enter on it

[trogdoro]

Yeah, some of the menus haven't been decoupled from emacs yet.

Try "ip" instead of "ls".

--Craig

On Sat, Sep 15, 2012 at 10:51 AM, jrichter notifications@github.com wrote:

I believe point is referring to point in emacs. I think this command is intended to be run from inside emacs. Try loading up emacs and typing: $ ls then double clicking on it, or pressing ctrl + enter on it

— Reply to this email directly or view it on GitHubhttps://github.com/trogdoro/xiki/issues/26#issuecomment-8586988.

[DougPuchalski]

+1 for fix

[trogdoro]

Jrichter was mostly right. It's one of the menus that is only applicable from inside your editor. It just shows the ls output on a file:

/tmp/foo.txt @ls/ | -rw-r--r-- 1 craig wheel 4B Nov 17 17:16 /tmp/foo.txt

When you do something like this from a xiki-enabled, it just delegates to the shell command directly:

/tmp/ $ ls

I should probably make it return a better error message.

What is the use-case you're trying to satisfy?

--Craig

On Fri, Nov 16, 2012 at 12:58 PM, Doug Puchalski notifications@github.com wrote:

+1 for fix

— Reply to this email directly or view it on GitHub.