xsh -r fails with error

[dsummersl]

When I run zsh -r I see the following in the lower left corner:

Error running timer: (el4r-ruby-error)

[alexlafroscia]

:+1: Also seeing this with the latest Xiki from Github

[trogdoro]

When I run zsh -r

I'm assuming you mean "xsh -r".

I just did a push - can you see if that fixed it? After you grab the latest xiki, run "xsh -reload" before you try again.

If that didn't fix it, can you run this and see what it says?

$ xsh -i -r

The -i flag makes it better at displaying error messages, since it doesn't create a cached process.

--Craig

On Thu, Apr 2, 2015 at 7:38 PM, Alex LaFroscia notifications@github.com wrote:

Also seeing this with the latest Xiki from Github

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

[dsummersl]

Yeah I meant xsh :)

The error is gone with this update! But...when I run xsh -i -r it just shows the text | See the key shortcuts at the bottom. (^G also runs in shell) with some keys at the bottom.

I use zsh, tried it in bash and it does the same thing.

[alexlafroscia]

I'm still seeing the same thing as @dsummersl, ^R doesn't actually show me any commands when running Xiki from ZSH (and I do mean ZSH).

[trogdoro]

Can you run this?

$ echo $SAVEHIST

If the output is 0, try running this:

$ SAVEHIST=1000

Then type a couple commands, then do ^R and see if it shows you them.

If this fixes it let me know, and I'll update xsh to temporarily set SAVEHIST if it's 0 in zsh.

--Craig

On Sat, Apr 4, 2015 at 11:28 AM, Alex LaFroscia notifications@github.com wrote:

I'm still seeing the same thing as @dsummersl https://github.com/dsummersl, ^R doesn't actually show me any commands in ZSH

— Reply to this email directly or view it on GitHub https://github.com/trogdoro/xiki/issues/138#issuecomment-89633711.

[dsummersl]

Darn, thats not it. My $SAVEHIST is already set to 1000, and the history command looks good.

[trogdoro]

Hmm... Can you run these 2 lines...

$ dir="$HOME/xiki/misc/logs" $ fc -W "$dir/shell_external_log.notes"

And then tell me what the contents of this file look like?

~/xiki/misc/logs/shell_external_log.notes

--Craig

[dsummersl]

The contents look good to my unfamiliar eyes:

: 1428162324:0;R
: 1428174041:0;./scripts/screen.sh
: 1428174054:0;echo $SAVEHIST
: 1428174068:7;xsh -r
: 1428174080:0;history
: 1428240308:0;dir="$HOME/xiki/misc/logs"
: 1428240316:3;man fc
: 1428240323:0;fc -W "$dir/shell_external_log.notes"
: 1428240337:14;vim ~/xiki/misc/logs/shell_external_log.notes
: 1428240353:0;xsh -r

[alexlafroscia]

@trogdoro I did that and the contents of that file was extremely long, and contained some command line stuff from a long time ago. I can't be sure that there's nothing in there that I wouldn't want to just put on the internet, so I will refrain from uploading it if that's alright. Is there something specific that I can look for?

[trogdoro]

Is there something specific that I can look for?

I just wanted to make sure there were some commands in the file. That's the file that xiki creates and then grabs your commands from, so it's good at least that seems to be functioning. At this point it'd probably be easiest for me to pair with one or both of you, so we can explore more easily. If this works, email me and we'll set up a time to screenshare on skype or google hangouts.

--Craig

On Sun, Apr 5, 2015 at 12:07 PM, Alex LaFroscia notifications@github.com wrote:

@trogdoro https://github.com/trogdoro I did that and the contents of that file was extremely long, and contained some command line stuff from a long time ago. I can't be sure that there's nothing in there that I wouldn't want to just put on the internet, so I will refrain from uploading it if that's alright. Is there something specific that I can look for?

— Reply to this email directly or view it on GitHub https://github.com/trogdoro/xiki/issues/138#issuecomment-89832438.

[alexlafroscia]

What's your email address? Or email me, alex [at] lafroscia.com

[trogdoro]

This should be fixed. Can you try again?

The problem was related to zsh putting special characters into the history file, and xsh choking silently while reading it in.

[alexlafroscia]

@trogdoro it's working for me now in ZSH

[dsummersl]

me too! thanks so much you all.