From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: dpleydel@univ-fcomte.fr
Cc: help-gnu-emacs@gnu.org,
Patrick Giraudoux <patrick.giraudoux@univ-fcomte.fr>
Subject: Re: Mysterious hidden end of line characters.
Date: Sat, 26 Jan 2008 21:41:12 +0100 [thread overview]
Message-ID: <6437D39B-1CA5-4BEA-9A6B-09A208114800@Web.DE> (raw)
In-Reply-To: <20080126171451.GB20762@univ-fcomte.fr>
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
Pete
The light at the end of the tunnel has been turned off due to budget
cuts.
next prev parent reply other threads:[~2008-01-26 20:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:14 Mysterious hidden end of line characters David
2008-01-26 19:21 ` Thierry Volpiatto
2008-01-26 19:54 ` David
2008-01-26 20:06 ` David
2008-01-26 20:08 ` David
[not found] ` <mailman.6584.1201377847.18990.help-gnu-emacs@gnu.org>
2008-01-27 6:10 ` Tim X
2008-01-27 7:17 ` kgdb in emacs Sanjeev Kumar.S
2008-01-27 8:26 ` Nick Roberts
2008-01-27 8:53 ` Sanjeev Kumar.S
2008-01-27 9:23 ` Nick Roberts
2008-01-27 10:17 ` Sanjeev Kumar.S
2008-01-27 10:51 ` Nick Roberts
2008-01-27 11:21 ` Sanjeev Kumar.S
2008-01-27 20:40 ` Nick Roberts
2008-01-26 20:41 ` Peter Dyballa [this message]
2008-01-30 15:04 ` Mysterious hidden end of line characters David
[not found] ` <mailman.6748.1201705322.18990.help-gnu-emacs@gnu.org>
2008-01-31 6:21 ` Tim X
2008-01-31 10:20 ` Thierry Volpiatto
2008-01-31 11:17 ` Peter Dyballa
2008-01-31 12:44 ` Thierry Volpiatto
2008-01-31 16:04 ` Thierry Volpiatto
2008-01-31 16:12 ` Thierry Volpiatto
2008-01-31 16:40 ` Thierry Volpiatto
2008-02-02 14:18 ` Thierry Volpiatto
2008-02-04 13:00 ` Thierry Volpiatto
2008-02-04 13:10 ` Thierry Volpiatto
[not found] <20080131144200.566493BC03B@ufc.univ-fcomte.fr>
2008-01-31 16:36 ` David
[not found] <20080131170759.CC0B71BC00C@ufc.univ-fcomte.fr>
2008-01-31 17:54 ` David
2008-01-31 18:28 ` Thierry Volpiatto
2008-02-01 12:54 ` David
2008-02-01 14:07 ` Thierry Volpiatto
2008-02-01 15:11 ` Thierry Volpiatto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6437D39B-1CA5-4BEA-9A6B-09A208114800@Web.DE \
--to=peter_dyballa@web.de \
--cc=dpleydel@univ-fcomte.fr \
--cc=help-gnu-emacs@gnu.org \
--cc=patrick.giraudoux@univ-fcomte.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).