unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
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 20:21:24 +0100	[thread overview]
Message-ID: <87odb8wfyj.fsf@thievol.homelinux.org> (raw)
In-Reply-To: <20080126171451.GB20762@univ-fcomte.fr> (David's message of "Sat,  26 Jan 2008 18:14:51 +0100")

Did you try running delete-trailing-white-space or picture-mode on your
files ?

David <dpleydel@univ-fcomte.fr> writes:

> I have a strange problem with invisible end of line characters.
>
> Yesterday I was trying to configure GRASS6.3 using the following
> single line of code.
>
>
> CFLAGS=-O2 ./configure \
> 	 --with-gdal=/usr/bin/gdal-config \
> 	 --with-tcltk \
> 	 --with-tcltk-includes=/usr/include/tcl8.4 \
> 	 --x-includes=/usr/include/X11 \
> 	--with-postgres-includes=/usr/include/postgresql \
> 	--with-freetype-includes=/usr/include/freetype2 \
> 	--x-includes=/usr/include/X11 \
> 	--x-libraries=/usr/lib/X11 \
> 	--with-libs=/usr/lib64 \
> 	--with-blas \
> 	--with-mysql \
> 	--with-mysql-includes=/usr/include/mysql \
> 	--with-cxx \
> 	--with-freetype \
> 	--with-freetype-includes=/usr/include/freetype2 \
> 	--with-readline \
> 	--with-sqlite \
> 	--with-tiff \
> 	--with-x \
> 	 --with-odbc \
> 	--enable-64bit \
> 	2>&1 | tee config_log.txt
>
>
> Normally the \ character tells the shell not to execute the line but
> to wait for the next line and execture them as one, so everything
> above is seen by the computer as a single line. Right?
>
> Well, not on my computer.  Each time I copied the lines from emacs to
> a terminal (konsole) for some reason the \ was being over riden and
> the terminal tried executing the code one line at a time. My effort to
> configure GRASS failled until I removed every \ and collapsed
> everything down to the following single line.
>
> CFLAGS=-O2 ./configure --with-gdal=/usr/bin/gdal-config --with-tcltk --with-tcltk-includes=/usr/include/tcl8.4 --x-includes=/usr/include/X11 --with-postgres-includes=/usr/include/postgresql --with-freetype-includes=/usr/include/freetype2 --x-includes=/usr/include/X11 --x-libraries=/usr/lib/X11 --with-libs=/usr/lib64 --with-blas --with-mysql --with-mysql-includes=/usr/include/mysql --with-cxx --with-freetype --with-freetype-includes=/usr/include/freetype2 --with-readline --with-sqlite --with-tiff --with-x --with-odbc --enable-64bit 2>&1 | tee config_log.txt
>
> A colleage then complained to me saying I had some kind of invisible
> character at the end of each line of a shell script (naturally, writen
> in emacs) that I'd sent him. He was having to guess where each of
> these nasty characters was and delete them line by line.  I think he
> has emacs on Ubuntu, I am running emacs21 on Debian etch.
>
> How might I try to identify what is going on here?
>
> cheers
> Dave
>
>
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>

-- 
A + Thierry
Pub key: http://pgp.mit.edu

  reply	other threads:[~2008-01-26 19:21 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 [this message]
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 ` Mysterious hidden end of line characters Peter Dyballa
2008-01-30 15:04   ` 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=87odb8wfyj.fsf@thievol.homelinux.org \
    --to=thierry.volpiatto@gmail.com \
    --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).