GNU TeXmacs - Bugs: bug #52891, TeXmacs does not start with a...
You are not allowed to post comments on this tracker with your current authentication level.
bug #52891: TeXmacs does not start with a weird error message
Submitter: | Victor Porton <porton> | ||
Submitted: | Mon 15 Jan 2018 01:04:28 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Item Group: | Error | Status: | Fixed |
Privacy: | Public | Assigned to: | vdhoeven |
Originator Name: | Open/Closed: | Closed | |
Release: | None | Release: | |
Fixed Release: | 1.99.12 | Fixed Release: | |
Keywords: |
Jump to the original submission
Sat 19 Oct 2019 12:34:04 AM UTC, comment #8: |
Joris van der Hoeven <vdhoeven> |
Wed 17 Jan 2018 11:03:22 PM UTC, comment #7: OK, I learned something from your bug :-) However, given that the issue does not occur on my system (ubuntu 16.04), I'm afraid I can't help sorting it out. Let us know if you come to understand the origin of the problem in your setup. |
Philippe Joyez <pjoyez> |
Wed 17 Jan 2018 07:39:02 PM UTC, comment #6: When a variable assignment is before the command (not on a separate line) sh or bash automatically export the variable for this command (not for the following lines of sh input).
|
Victor Porton <porton> |
Wed 17 Jan 2018 07:28:16 PM UTC, comment #5: Oh, I see. It wasn't clear that was input. Anyway, I still think I have a point since the instructions are to :
|
Philippe Joyez <pjoyez> |
Wed 17 Jan 2018 06:27:42 PM UTC, comment #4: The following is NOT what it prints, but it is what I type in the Bash command line:
|
Victor Porton <porton> |
Wed 17 Jan 2018 06:21:13 PM UTC, comment #3: Yes I saw, and this is precisely why I suspect something is wrong with the PATH: I find it strange that it prints PATH=$PATH:... where $PATH has not been expanded. |
Philippe Joyez <pjoyez> |
Wed 17 Jan 2018 03:35:28 PM UTC, comment #2: Philippe, you see that I do have PATH setting in my bug report. |
Victor Porton <porton> |
Wed 17 Jan 2018 07:50:49 AM UTC, comment #1: It looks like a misconfiguration of the PATH so that the wrapper script does not find the executable. Maybe there was an error while manually setting up the PATH? This installation procedure is not very user-friendly...
|
Philippe Joyez <pjoyez> |
Mon 15 Jan 2018 01:04:28 AM UTC, original submission:
I have installed http://www.texmacs.org/Download/ftp/tmftp/generic/TeXmacs-1.99.6-B.tar.gz into /usr/local/stow/TeXmacs-1.99.6-10945-i386-pc-linux-gnu
|
Victor Porton <porton> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-10-19 | vdhoeven | Status | Need Info | Fixed | |
Assigned to | None | vdhoeven | |||
Open/Closed | Open | Closed | |||
Fixed Release | None | 1.99.12 | |||
2018-01-17 | pjoyez | Status | None | Need Info |
Powered by Savane 3.13-f8d8.
Corresponding source code
Hi Victor,
I don't know if you still experience this bug, but it probably is indeed related with the way you set things up. I recently tested TeXmacs on some machine at another university and I had to do a 'rehash' after changing the PATH before being able to use TeXmacs.
So please carefully proceed as follows:
- Redefine the TEXMACS_PATH and PATH using export or setenv.
- I prefer that you do PATH=[path-to-texmacs]:$PATH
to be sure that the target version of TeXmacs has priority.
- Do a 'hash' or 'rehash' before launching TeXmacs
if necessary.
For the moment, I close the bug.
Please re-open it if necessary, while providing more details.
Best wishes, --Joris