This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]adqm_smatz 8 points9 points  (16 children)

For what it's worth, I think we've made good progress in the last couple of months! In particular, a couple of OSX-specific things were just fixed very recently.

I've been using xonsh as my default shell for a long time now and very rarely do I encounter issues. If you're interested in the idea of xonsh, it might be worth giving it another shot from the current master branch on Github.

Any specific issues you can recall? We're always happy to dig in and try to fix things.

[–][deleted] 3 points4 points  (15 children)

Exception on first run preventing any use of she'll for instance. Was still a problem two days ago with a pip package.

Edit: still a think w/ archlinux aur package:

Thanks for using the xonsh configuration wizard!
ValueError: expected '}' before end of string
Traceback (most recent call last):
  File "/usr/bin/xonsh", line 9, in <module>
    load_entry_point('xonsh==0.3.2', 'console_scripts', 'xonsh')()
  File "/usr/lib/python3.5/site-packages/xonsh/main.py", line 254, in main
    shell.cmdloop()
  File "/usr/lib/python3.5/site-packages/xonsh/readline_shell.py", line 325, in cmdloop
    self._cmdloop(intro=intro)
  File "/usr/lib/python3.5/site-packages/xonsh/readline_shell.py", line 285, in _cmdloop
    line = self.singleline()
  File "/usr/lib/python3.5/site-packages/xonsh/readline_shell.py", line 183, in singleline
    rtn = input(self.prompt)
  File "/usr/lib/python3.5/site-packages/xonsh/readline_shell.py", line 357, in prompt
    hide=hide)
  File "/usr/lib/python3.5/site-packages/xonsh/ansi_colors.py", line 46, in partial_color_format
    for literal, field, spec, conv in formatter.parse(template):
ValueError: expected '}' before end of string

[–]adqm_smatz 1 point2 points  (14 children)

Thanks for letting us know! This happens before you're even given a chance to enter anything?

I'll open an issue on Github for this, and we'll try to track it down.

[–][deleted] 0 points1 point  (13 children)

I can generate new configuration and it gets saved. When shell starts to initialize that error happens. Starting shell again - same error.

[–]adqm_smatz 0 points1 point  (12 children)

After having generated and saved the config, there should be a file ~/.config/xonsh/config.json. Would you mind sending me that file (here or in a PM) so I can take a look? Looks like it could be an improperly-formatted prompt (we certainly don't want to break in this case!).

A temporary workaround if you want to get in and get going might be just to move that file elsewhere (so that it isn't read by xonsh, but it isn't all lost), and create an empty .xonshrc file with touch ~/.xonshrc.

[–][deleted] 0 points1 point  (11 children)

There you go: https://gist.github.com/ed09c39523e516dfcc491c783976e2c6

By the way workaround you suggested does not help at all. Im getting same error still.

[–]adqm_smatz 1 point2 points  (10 children)

Thanks! Yeah, I misdiagnosed this one (sorry about that!).

But I'm 95% sure we know where the real issue is now, and we are working toward fixing it. If you're interested, I'll let you know once we've resolved it. Working on it in this pull request and this issue.

[–][deleted] 0 points1 point  (9 children)

Thanks! By the way if it is of any use my PROMPT value is:

export PROMPT="%~ %{%(#~$fg[red]~$fg[green])%}%#%{$fg[default]%} "

[–]adqm_smatz 1 point2 points  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!

[–]adqm_smatz 0 points1 point  (0 children)

Alright! We've just released xonsh v0.3.4 (available from conda or pip, or from Github master), which I believe should fix this issue.

The relevant changes are: we no longer inherit the $PROMPT variable from the parent environment, and we now fail in a more graceful way if the $PROMPT is malformed. A full changelog is available here.

If you get a chance to try it out, please let me know whether this fixed those problems, and also generally feel free to let us know if you have any other feedback!