purcell exec-path-from-shell issues

purcell / exec-path-from-shell

Make Emacs use the $PATH set up by the user's shell

Other

1.43k stars 82 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Take care of the possible absence of SHELL env.

#20 syl20bnr closed 9 years ago
2
clarifying some documentation

#19 jasonhemann closed 9 years ago
1
Initialize during package load?

#18 rnkn closed 10 years ago
2
Consider removing "-i" from the shell startup args

#17 purcell closed 10 months ago
2
exec-path-from-shell-getenvs fails if $MANPATH is not set and set -e nounset

#16 j0xaf closed 10 years ago
1
exec-path paths order reversed

#15 ghost closed 10 years ago
7
Customizable args

#14 swsnr closed 10 years ago
3
Option to disable -i

#13 swsnr closed 10 years ago
2
Shell / Compile etc PATH not set after running exec-path-from-shell-initialize

#12 jasonm23 closed 10 years ago
4
Causes (Cocoa) Emacs to fail on OS X 10.9 (w/ bash shell when MANPAGE env var is empty)

#11 RobotDisco closed 10 years ago
21
Fails with tcsh when a variable is unset

#10 purcell closed 10 years ago
0
Support for fish shell (path-separator)

#9 ghost closed 10 years ago
26
package install problems

#8 rebcabin closed 11 years ago
1
tcsh compatibility

#7 apchamberlain closed 11 years ago
1
Empty variables break initialization

#6 ghost closed 11 years ago
9
Fix NUL character introducing escape secuence for octal values

#5 uu1101 closed 11 years ago
15
Initialize $EMAIL

#4 swsnr closed 11 years ago
2
Autoload issue?

#3 NicholasKirchner closed 11 years ago
8
Initialize MANPATH

#2 swsnr closed 12 years ago
1
Make parsing more reliable

#1 swsnr closed 12 years ago
3