On 03/03/13 03:23 AM, Sven Joachim wrote: > On 2013-03-01 05:44 +0100, Daniel Dickinson wrote: > >> Package: elserv >> Version: 0.4.0+0.20011203cvs-17.1 >> Followup-For: Bug #701949 >> >> Upon googling (well really duckduckgo) I discovered that heredocs (e.g >> the cat << EOF >path.el) are lazy evaluated in bash, which I think >> means the parentheses get evaluated before the cat, which screws up >> the heredoc (empty). > > I'm not sure what you mean by "lazy evaluated", but maybe it's the fact > that the text in the heredoc is subject to parameter expansion, command > substitution and arithmetic expansion. Those does not occur here.
Ah, ok. I assume you are sure of that. > >> In any event replacing there heredoc with echo " >> ( setq ... ) >> " >path.el works around the issue. > > You would need to use single quotes then, since double quotes occur in > the text. Actually I use double quotes and backslash the quotes in the command in the heredoc. > > Does the following script work for you? If not, can you run it under > "strace -f" to see what goes wrong? > That scripts works for me in an xfce4-terminal right now, however when I tried it when the error was occurring (before I submitted the bug report), it did not, so I am rather puzzled. There is apparently some change in my environment for reasons that make no sense to me (as in I don't know where to start looking; nothing in env or set from the affected -el scripts shows anything that stands out and stdin should come from the <<EOF). Regards, Daniel -- <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
