|
From: | Peter Dyballa |
Subject: | Re: Mysterious hidden end of line characters. |
Date: | Sat, 26 Jan 2008 21:41:12 +0100 |
Am 26.01.2008 um 18:14 schrieb David:
How might I try to identify what is going on here?
You could have used a *-dos or *-mac encoding, which have two characters as line endings: line feed-carriage return or carriage return-line feed. This might cause trouble. You can check this by clicking with the mouse cursor onto the encoding marker in mode-line – at least in GNU Emacs 22. Otherwise there is describe-encoding.
But the *BIG* question is: why and for what do you need some external terminal application?!
In GNU Emacs you can imitate your behaviour by creating a *shell* buffer (M-x shell RET). In this *shell* buffer you have all that available what GNU Emacs can do, for example "flattening" your configure invocation.
It's possible too to use the *scratch* buffer to prepare such a long and complicated line.
And finally, the top choice: use compile! M-x compile RET and remove whatever you see in minibuffer, then paste (yank) the configure invocation as one line. You're still able to edit this line, isearch, whatever – and remove that "2>&1 | tee config_log.txt" ballast! Press RET. Isn't what you now see much nicer with the colourful faces? You can save that buffer – and you better kill it, that compile does not overwrite it when you start to really compile the software!
GNU Emacs can even remember your compile commands (M-x compile RET UP UP). IMO it's better not to rely on bash and explicitly use
env <whichever environment settings> <the command>And there is one situation when it's rather useful to configure in *compilation* buffer: when the line of input is too long for the shell to handle interactively.
-- Greetings PeteThe light at the end of the tunnel has been turned off due to budget cuts.
[Prev in Thread] | Current Thread | [Next in Thread] |