unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gelika PAPP-RAFFY <gelika.papp-raffy@st.com>
To: <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: RE: hexl-mode, while saving encoding problem
Date: Fri, 9 Nov 2007 09:36:04 +0100	[thread overview]
Message-ID: <000901c822ab$944a2be0$72a83c0a@mun.st.com> (raw)
In-Reply-To: <453348FC-FB45-4EF4-841A-76C18E468884@Web.DE>

Thanks for your tip, it works fine.

Now I have a very basic problem: My emacs installation is on a virtual
machine with no internet access, so that I can not report the bug from emacs
directly.
If this is to be corrected as a bug, then there should be also other
compressed audio files added to this list (I didn't try to edit them so I am
not sure they would save wrongly): .wma, .aac, .m4a and probably also ogg
vorbis files, I don't know the extensions.

Thank you for the prompt support, I had been searching the net for quite a
while now *what* could be corrupting and how not to corrupt my files :-))))

Gelika

> -----Original Message-----
> From: Peter_Dyballa@Web.DE [mailto:Peter_Dyballa@Web.DE] 
> Sent: Thursday, November 08, 2007 4:40 PM
> To: Gelika PAPP-RAFFY
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: hexl-mode, while saving encoding problem
> 
> 
> Am 08.11.2007 um 16:03 schrieb Gelika PAPP-RAFFY:
> 
> > I am editing binary files with emacs (ID3 tags in .mp3 files).
> > I use the hexl-mode.
> > When I want to save my modifications I get the question "Selet  
> > coding system" and it is asking me to choose between several like  
> > undecided-unix, mule-utf-8, etc.
> 
> There is a variable, file-coding-system-alist, that also lists file  
> name extensions for which no-conversion is applied upon reading or  
> writing. Obviously no-one has edited an MP3 file before, so this is  
> not mentioned there.
> 
> It might be worth to write a bug report and ask for this enhancement.
> 
> To solve your problem now you can add to your init file this code:
> 
> 	(add-to-list 'file-coding-system-alist '("\\.mp3\\'" . 
> no-conversion))
> 
> To have it set at once put the line into the *scratch* buffer,  
> position the cursor at its end and press C-j. Then open, edit, and  
> save the MP3 file again.
> 
> --
> Greetings
> 
>    Pete
> 
> "Isn't vi that text editor with two modes... one that beeps and one
> that corrupts your file?" -- Dan Jacobson, on comp.os.linux.advocacy
> 
> 

  reply	other threads:[~2007-11-09  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 15:03 hexl-mode, while saving encoding problem Gelika PAPP-RAFFY
2007-11-08 15:40 ` Peter Dyballa
2007-11-09  8:36   ` Gelika PAPP-RAFFY [this message]
2007-11-09  9:54     ` Peter Dyballa
  -- strict thread matches above, loose matches on Subject: below --
2007-11-08 16:33 martin rudalics
     [not found] <mailman.3130.1194534207.18990.help-gnu-emacs@gnu.org>
2007-11-08 19:02 ` Stefan Monnier
     [not found] <mailman.3165.1194597393.18990.help-gnu-emacs@gnu.org>
2007-11-10  0:31 ` Mark Hood

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='000901c822ab$944a2be0$72a83c0a@mun.st.com' \
    --to=gelika.papp-raffy@st.com \
    --cc=Peter_Dyballa@Web.DE \
    --cc=help-gnu-emacs@gnu.org \
    /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).