elisp to change line endings for new remote file

elisp to change line endings for new remote file

[yary]

Hello,

Hoping someone can write a line or two of elisp for my .emacs file
that will set the line endings to Unix for any new file opened via
tramp. I'm using GNU Emacs 23.0.60.1 on Windows, often creating Unix
files via plink, and usually forgetting to change the line endings
from DOS when I do. If you've already solved this in your setup,
please share.

Thanks much!

Re: elisp to change line endings for new remote file

[Giorgos Keramidas]

On Mon, 6 Oct 2008 10:07:50 -0700 (PDT), yary <not.com@gmail.com> wrote:
> Hello,
> Hoping someone can write a line or two of elisp for my .emacs file
> that will set the line endings to Unix for any new file opened via
> tramp. I'm using GNU Emacs 23.0.60.1 on Windows, often creating Unix
> files via plink, and usually forgetting to change the line endings
> from DOS when I do. If you've already solved this in your setup,
> please share.

You can change teh line endings later.  Type `C-x RET f' and then, at
the prompt for a coding system, type the name of a coding system with
the "-dos" or "-unix" suffix.

For example, to convert a remote file to UTF-8 with Unix-style line
endings, you can visit the file in a buffer and type:

    C-x RET f utf-8-unix RET

Re: elisp to change line endings for new remote file

[Kevin Rodgers]

yary wrote:
> Hoping someone can write a line or two of elisp for my .emacs file
> that will set the line endings to Unix for any new file opened via
> tramp. I'm using GNU Emacs 23.0.60.1 on Windows, often creating Unix
> files via plink, and usually forgetting to change the line endings
> from DOS when I do. If you've already solved this in your setup,
> please share.

 From the "Text and Binary" node of the Emacs manual:

    When you use NFS, Samba, or some other similar method to access file
systems that reside on computers using GNU or Unix systems, Emacs
should not perform end-of-line translation on any files in these file
systems--not even when you create a new file.  To request this,
designate these file systems as "untranslated" file systems by calling
the function `add-untranslated-filesystem'.  It takes one argument: the
file system name, including a drive letter and optionally a directory.
For example,

      (add-untranslated-filesystem "Z:")

designates drive Z as an untranslated file system, and

      (add-untranslated-filesystem "Z:\\foo")

designates directory `\foo' on drive Z as an untranslated file system.

    Most often you would use `add-untranslated-filesystem' in your
`.emacs' file, or in `site-start.el' so that all the users at your site
get the benefit of it.


-- 
Kevin Rodgers
Denver, Colorado, USA

Re: elisp to change line endings for new remote file

[Peter Dyballa]

Am 06.10.2008 um 19:07 schrieb yary:

> I'm using GNU Emacs 23.0.60.1 on Windows, often creating Unix
> files via plink, and usually forgetting to change the line endings
> from DOS when I do.


There is before-save-hook. It could be (time-stamp). You could add  
(via the customisation interface) another function that changes from  
DOS to UNIX file endings, (set-buffer-file-coding-system coding- 
system &optional force nomodify).

Another option is to put into your init file:

	(prefer-coding-system	 'utf-8-unix)

although I doubt that this would change *existing* line endings.  
Can't plink be taught to prefer UNIX style line endings? If it's so  
dumb than you should learn to prefer GNU Emacs and TRAMP ...

--
Greetings

   Pete

Upgraded, adj.:
	Didn't work the first time.

Re: elisp to change line endings for new remote file

[yary]

Thanks all. I already knew about add-untranslated-filesystem. tramp/
plink is smart enough to not translate its files, so that's not the
solution for creating new files with unix line endings.

On Oct 7, 2:43 am, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 06.10.2008 um 19:07 schrieb yary:
...
> There is before-save-hook. It could be (time-stamp). You could add  
> (via the customisation interface) another function that changes from  
> DOS to UNIX file endings, (set-buffer-file-coding-system coding-
> system &optional force nomodify).
...
That seems close to the right thing, but I'd want to call after
opening a new "tramp" file, not before saving- if it has MS-DOS line
endings already, I want to change it manually.

> Another option is to put into your init file:
>
>         (prefer-coding-system    'utf-8-unix)
>
> although I doubt that this would change *existing* line endings.  

That's also a good answer, as I don't want to change existing endings-
just want to make my new files correct for the platform. Though I'd
have a problem when I opened up a new file on the Windows side.

(Curse that CR, how many thousands of hours have been wasted due to
you...)

Re: elisp to change line endings for new remote file

[Kevin Rodgers]

yary wrote:
> Thanks all. I already knew about add-untranslated-filesystem. tramp/
> plink is smart enough to not translate its files, so that's not the
> solution for creating new files with unix line endings.

Then where do the DOS line endings come from?

When you visit a new file via tramp, what does `C-h v 
buffer-file-coding-system'
report?  Did you actually add the file's directory (or an ancestor 
directory) to
untranslated-filesystem-list?

-- 
Kevin Rodgers
Denver, Colorado, USA

Re: elisp to change line endings for new remote file

[yary]

On Oct 7, 6:29 pm, Kevin Rodgers <kevin.d.rodg...@gmail.com> wrote:

> When you visit a new file via tramp, what does `C-h v
> buffer-file-coding-system'
> report?  Did you actually add the file's directory (or an ancestor
> directory) to
> untranslated-filesystem-list?
>
> --
> Kevin Rodgers
> Denver, Colorado, USA

Sorry took so long to follow up.
(add-untranslated-filesystem "/plink:")
as suggested, in ~/.emacs did the trick