summaryrefslogtreecommitdiff
path: root/elisp/geiser-syntax.el
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2013-04-13 05:22:20 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2013-04-13 05:22:20 +0200
commit3b5397c8dad34f9dfe83c2c44eeece0de9097df3 (patch)
tree6a2d8e8b71d2e806dd4183a187e65db45b0b3a35 /elisp/geiser-syntax.el
parentd494b97c34386470fa9b7ee7ddcc63c41b8c51ff (diff)
downloadgeiser-chez-3b5397c8dad34f9dfe83c2c44eeece0de9097df3.tar.gz
geiser-chez-3b5397c8dad34f9dfe83c2c44eeece0de9097df3.tar.bz2
A better solution to the funky filename problem
So, the problem was that our regexp for a Racket prompt didn't take into account that filenames could contain white spaces: "@[^ ]*> ". A simple solution was accepting them: "@[^>]+> " won't work because '>' is also a valid character in filenames, so we went for "@.*> ". The drawback is that finding the beginning of the prompt (e.g. in C-a) fails when you're writing things like: racket@foo bar.rkt> (> 2 3) because here comint believes that the prompt is "racket@foo bar.rkt> (> " And that could have side-effects elsewhere. So what i've done is simply changing the way white-space is (not) printed in the prompt, substituting it by underscores. That way, whe can go back to the initial regexp, comint doesn't get confused, and users can easily infer that "@foo_bar.rkt>" is actually referring to their "foo bar.rkt" file.
Diffstat (limited to 'elisp/geiser-syntax.el')
0 files changed, 0 insertions, 0 deletions