unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mark Hood <invalid@invalid.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: hexl-mode, while saving encoding problem
Date: 09 Nov 2007 16:31:25 -0800	[thread overview]
Message-ID: <ygfwssrkkki.fsf@invalid.invalid> (raw)
In-Reply-To: mailman.3165.1194597393.18990.help-gnu-emacs@gnu.org

I often have to edit binary files of various types and run into the
same problem.  The following works for me in those situations:

(setq default-enable-multibyte-characters nil)

       reply	other threads:[~2007-11-10  0:31 UTC|newest]

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

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=ygfwssrkkki.fsf@invalid.invalid \
    --to=invalid@invalid.invalid \
    --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).