〚Ian‖telegram〛 If I hit ^C I go back to a normal prompt, if I hit Enter it'll crash.
〚xiaqqaix‖telegram〛 @krader1961 the problem with a pure-text format is that anything that is not append can require rewriting the entire file
〚xiaqqaix‖telegram〛 ok, the crash log is a symptom not the cause
〚Ian‖telegram〛 I was assuming that would be the case.
〚Ian‖telegram〛 Hmm, on my main system its 8MB.
〚xiaqqaix‖telegram〛 @krader1961 i personally appreciate the fact that using a real database allows elvish to keep my shell history forever :)
〚Ian‖telegram〛 elvish -buildinfo
Version: v0.13.1-238-gf7f2a27
Go version: go1.14.1
Reproducible build: true
Version: v0.13.1-238-gf7f2a27
Go version: go1.14.1
Reproducible build: true
〚Ian‖telegram〛 Built it via my update module which just does a go get
〚Paradox460‖telegram〛 fish uses an LRU and has 256k uniques max
〚xiaqqaix‖telegram〛 hmm, that's a recent elvish version built a recent go compiler...
〚Ian‖telegram〛 It's why I made that update module in the first place, got sick of accidentally running something old. Now my terminal yells at me if that's the case 😄 .
〚Ian‖telegram〛 It's a pretty stock Ubuntu 18.04 system, there's a chance work admins have done something surprising but it's not obvious.
〚xiaqqaix‖telegram〛 the error seems to come from the rpc client code that talks to the daemon: https://github.com/elves/elvish/blob/f7f2a271b66b66b48c139f3698076d5387a34a10/pkg/daemon/client.go#L150
〚Ian‖telegram〛 hmm, I did install go with a snap on this system
〚Ian‖telegram〛 That's the only thing that I can think of that might be "weird"
〚xiaqqaix‖telegram〛 if you cd /tmp/elvish-(id -u), do you see several files starting with daemon.log-?
〚xiaqqaix‖telegram〛 aha (re @Ian: hmm, I did install go with a snap on this system)
〚Ian‖telegram〛 ...uh oh
〚xiaqqaix‖telegram〛 can you try this prebuilt binary? https://dl.elv.sh/linux-amd64/elvish-HEAD.tar.gz
〚xiaqqaix‖telegram〛 ... and see if you can still reproduce it, i mean
〚Ian‖telegram〛 yup
〚Ian‖telegram〛 that works fine
〚Ian‖telegram〛 Well, I shouldn't be surprised, every time I've tried to be lazy and use a snap it's backfired in really weird and obscure ways.
〚xiaqqaix‖telegram〛 i wonder what's funny with the snap version of the go compiler
〚xiaqqaix‖telegram〛 mismatch of payload size is something that could cause errors that you saw
〚Ian‖telegram〛 Not sure...I already uninstalled it but let me try and find out.
〚xiaqqaix‖telegram〛 i wonder if the PPA build was built with Go from snap
〚xiaqqaix‖telegram〛 :)
〚Ian‖telegram〛 lol
〚Ian‖telegram〛 An Ubuntu 18.04 system at home has the PPA and works fine with ^R.
〚xiaqqaix‖telegram〛 try bash -c ulimit
See also elves/elvish#596 which points out that it is easy to create a corruputed command history boltdb file.
@zzamboni, I was wondering why my prompt changed its colors every time I started a new elvish session. Even when nothing in my environment was changed. I had copied most of your elvish config; at least as published on github. Then I noticed this in the documentation:
session (a glyph with a unique color for the current session, based on its PID). Which caused me to read your -session-color function.
Do you actually use the
session style? I can appreciate it from a “what if” perspective. But it seems to me to be completely unusable with respect to producing usable results. That is, prompts that are readable.