-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
capture basedir #90
Comments
Is the REPL working for you otherwise? |
Yes. I haven't spent a lot of hours in it yet. |
Can you please evaluate print("OK" * normpath(joinpath(VERSION ≤ v"0.7-" ? JULIA_HOME : Sys.BINDIR, Base.DATAROOTDIR, "julia", "base")))
and post the results for both here? |
The *Warnings* buffer doesn't open in uxterm Emacs, only in GUI Emacs, replacing in julia-repl-1.2.0/julia-repl.el the GUI Emacs
pasting
pasting uxterm Emacs
uxterm Julia
|
Does this look like a GUI Emacs bug or MELPA packages' bugs? Can you reproduce on Slackware-current? |
This is weird, it looks like an issue related to Unicode. Do UTF8 symbols work otherwise in the REPL? |
GUI Emacs (julia-repl)
uxterm Emacs (julia-repl)
This surprised me a bit. [ess-18.10.2] GUI Emacs (R)
uxterm Emacs (R)
uxterm R
|
I am not sure this is a bug with julia-repl. Please investigate; and let me know if there is a workaround in julia-repl I can help with. I could of course replace |
In GUI Emacs (julia) \le [TAB] returns this In uxterm Emacs (julia) \le [TAB] returns this In GUI Emacs (julia-repl) \le [TAB] and \leq [TAB] returns this In uxterm Emacs (julia-repl) \le [TAB] and \leq [TAB] both return this |
Is Which OS is this? Also, bash 4.3 is rather old, which may not be directly related but something else on your system may be. |
Incidentally, are you starting julia-repl after starting an ESS process? If yes, please
and see what happens. |
Yes, julia-mode was a dependency for ess. ess 18.10.2 installed
Index of /slackware/slackware-14.2/patches/source
Its' not the Emacs configure arguments.
No. GUI Emacs (julia-repl) Going into the *Scratch* buffer and typing
In the *julia* buffer typing That is done of course after the *Warnings* buffer appeared. uxterm Emacs (julia-repl) Going into the *Scratch* buffer and typing
I wonder if the bug shows elsewhere. |
For Emacs GUI (julia-repl) adding this code to ~/.emacs.d/init.el works for the rendering.
Yes, let's do that for the Warning. cf: #90 (comment) The above added hook to ~/.emacs.d/init.el has no effect on the disparity in the GUI vs. terminal ESS (R) Error output caused by the
|
Here's the Slackware-14-2 (from patches) emacs-26.3 package creation script. If the GUI Emacs julia-repl unicode rendering issue doesn't show up in other GNU/Linux distributions, or other OSes, then this might be added to the README.md specifically for Slackware Linux. If Emacs is running in a GUI and you are experiencing problems with Unicode characters in the Julia REPL, place this in your Emacs initialization files (eg (if (display-graphic-p)
(add-hook 'term-exec-hook
(function
(lambda ()
(set-buffer-process-coding-system 'utf-8-unix 'utf-8-unix))))) |
So What's the default value if you don't set it (eg eval (process-coding-system (get-buffer-process (current-buffer))) in a term buffer)? |
Yes, in the hook added in ~/.emacs.d/init.el.
With the hook removed from ~/.emacs.d/init.el. GUI Emacs (julia) (iso-latin-1-unix . iso-latin-1-unix) uxterm Emacs (julia) (utf-8-unix . utf-8-unix) FWIW, here is my initialisation file after installing the MELPA packages.
What about rewriting the conditional Should the README.md be up-to-date in promoting the use of ~/.emacs.d/init.el? |
I am very happy to update the README if this is a general problem but your setup seems to be an outlier (and more importantly I would prefer to understand why first), so I am not sure it would benefit users. These days you really have to go out of your way to get something other than UTF8. An environment variable perhaps? Do you have any of |
link removed Nov 10, 2020 But should the conditional
I followed the recommended instructions when installing Slackware-12.2 which defaulted to en_US. I noticed in console mode that after running export LANG=da_DK.UTF-8 that some of the Danish characters did not render properly, so with subsequent Slackware releases' installations I have never set $LANG to a unicode variant. @willysr I don't know what Slackware-current recommends? Incidentally, this perplexes me a bit. uxterm Emacs (julia-repl)
xterm
uxterm
Link to emacs package creation script in #90 (comment). Can't enlighten you much on that one, but in uxterm & xterm (for this issue) I've been typing
|
Sorry, i never used emacs |
@willysr I meant about the install $LANG setting. |
@tpapp further reading (Slackware $LANG setting) search for 'lang.csh' |
in slackware-current: in slackware 14.2: |
Starting the GUI Emacs from uxterm without the conditional |
If $LANG is a non-unicode variant. For GUI Emacs export (eg No coding patches needed, the README.md might be edited adding something like the above. @willysr Thanks, I can't envisage any future GUI issues when the install $LANG is a unicode variant
xterm (with exported unicode LANG) GUI Emacs (julia-repl)
starting emacs from the command-line, switching modes
returns switching modes again
xterm (with exported unicode LANG) Emacs (julia-repl)
starting emacs from the command-line and pasting switching modes
returns switch modes again cf: #90 (comment) & #90 (comment) xterm (with exported unicode LANG) GUI Emacs ESS (R)
starting emacs from the command-line the Error message is identical to when run inside uxterm
Lisp Eval M-: |
adding this to ~/.emacs.d/init.el works (if (display-graphic-p)
(setenv "LANG" "da_DK.UTF-8" (set-locale-environment "da_DK.UTF-8"))) closing |
Thanks for investigating this. I am not sure it is worth documenting this quirk of 4-year old version of Slackware for a general audience, but if people run into this I can just refer them to this issue. |
M-x julia-repl
generates in a *Warnings* buffer the below.Warning (emacs): could not capture basedir for Julia executable julia
The text was updated successfully, but these errors were encountered: