unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Brian Adkins <lojicdotcom@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Can't paste from files with .arc extension
Date: Fri, 7 Mar 2008 09:43:57 -0800 (PST)	[thread overview]
Message-ID: <bfcc81ca-6eba-49c3-a17b-fe01030911bd@8g2000hse.googlegroups.com> (raw)
In-Reply-To: a32da360-d794-4cdf-8c1d-302ceb82c827@m34g2000hsc.googlegroups.com

On Mar 7, 12:40 pm, Brian Adkins <lojicdot...@gmail.com> wrote:
> Thanks to Peter, I kept poking around auto-mode-alist and it pointed
> me to auto-coding-alist:
>
> auto-coding-alist is a variable defined in `mule.el'.
> Its value is
> (("\\.\\(arc\\|zip\\|lzh\\|lha\\|zoo\\|[jew]ar\\|xpi\\|exe\\|rar\\|ARC\
> \|ZIP\\|LZH\\|LHA\\|ZOO\\|[JEW]AR\\|XPI\\|EXE\\|RAR\\)\\'" . no-
> conversion)
>  ("\\.\\(sx[dmicw]\\|odt\\|tar\\|tgz\\)\\'" . no-conversion)
>  ("\\.\\(gz\\|Z\\|bz\\|bz2\\|gpg\\)\\'" . no-conversion)
>  ("\\.\\(jpe?g\\|png\\|gif\\|tiff?\\|p[bpgn]m\\)\\'" . no-conversion)
>  ("\\.pdf\\'" . no-conversion)
>  ("/#[^/]+#\\'" . emacs-mule))
>
> Documentation:
> Alist of filename patterns vs corresponding coding systems.
> Each element looks like (REGEXP . CODING-SYSTEM).
> A file whose name matches REGEXP is decoded by CODING-SYSTEM on
> reading.
>
> The settings in this alist take priority over `coding:' tags
> in the file (see the function `set-auto-coding')
> and the contents of `file-coding-system-alist'.
>
> You can customize this variable.

Yep, that did the trick! I clicked on the customize link in the help
(ya gotta love how integrated code, variables, help, etc. is in emacs)
and removed arc from the 'no-conversion' association.

Thanks for your time in pointing me down the right road Peter.


  reply	other threads:[~2008-03-07 17:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 14:00 Can't paste from files with .arc extension Brian Adkins
2008-03-07 14:07 ` Brian Adkins
2008-03-07 14:26   ` Brian Adkins
2008-03-07 15:10     ` Peter Dyballa
     [not found]     ` <mailman.8503.1204902612.18990.help-gnu-emacs@gnu.org>
2008-03-07 15:32       ` Brian Adkins
2008-03-07 16:05         ` Peter Dyballa
     [not found]         ` <mailman.8510.1204905941.18990.help-gnu-emacs@gnu.org>
2008-03-07 16:18           ` Brian Adkins
2008-03-07 16:22             ` Brian Adkins
2008-03-07 17:02             ` Peter Dyballa
     [not found]             ` <mailman.8514.1204909345.18990.help-gnu-emacs@gnu.org>
2008-03-07 17:27               ` Brian Adkins
2008-03-07 17:40 ` Brian Adkins
2008-03-07 17:43   ` Brian Adkins [this message]
2008-03-08 13:04     ` Eli Zaretskii
     [not found]     ` <mailman.8550.1204981470.18990.help-gnu-emacs@gnu.org>
2008-03-08 15:27       ` Brian Adkins
2008-03-08 20:31         ` Eli Zaretskii
2008-03-08 21:21         ` Stefan Monnier
2008-03-08 22:45           ` Peter Dyballa
2008-03-09  4:15             ` Eli Zaretskii
2008-03-09  9:26               ` Peter Dyballa
2008-03-09 22:06                 ` Eli Zaretskii
2008-03-09 22:14                   ` Peter Dyballa
2008-03-09 22:41                     ` Eli Zaretskii
2008-03-09 22:55                       ` Peter Dyballa
     [not found]         ` <mailman.8569.1205008330.18990.help-gnu-emacs@gnu.org>
2008-03-09  0:16           ` Brian Adkins
2008-03-09  4:21             ` Eli Zaretskii
2008-03-07 18:59   ` 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=bfcc81ca-6eba-49c3-a17b-fe01030911bd@8g2000hse.googlegroups.com \
    --to=lojicdotcom@gmail.com \
    --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).