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: Sat, 8 Mar 2008 16:16:01 -0800 (PST)	[thread overview]
Message-ID: <49e22913-cbe4-4aad-8882-39dd014fbf87@u69g2000hse.googlegroups.com> (raw)
In-Reply-To: mailman.8569.1205008330.18990.help-gnu-emacs@gnu.org

On Mar 8, 3:31 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: Brian Adkins <lojicdot...@gmail.com>
> > Date: Sat, 8 Mar 2008 07:27:32 -0800 (PST)
>
> > I thought that inclusion of the .arc extension in the auto-coding-
> > alist meant that emacs considered the file to be binary and thus would
> > not paste contents into another application. Are you saying that the
> > expected behavior is for emacs to paste anyway?
>
> Yes, I don't see any reason why printable characters from a binary
> file could not be pasted into another application.  Emacs has a way of
> dealing with characters that cannot be safely put into the X selection
> (it replaces them with `?'s or some such), if that's what you thought
> could prevent copy-paste.
>
> So I encourage you to report this as a bug.  Thanks.

I went ahead and filed the bug report as you suggested in case the
desired behavior is to paste from no-conversion files; however, in my
case, I think the proper thing to do is to remove .arc from the list
since in my case a .arc file is simply a file containing a dialect of
Lisp.


  parent reply	other threads:[~2008-03-09  0:16 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
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 [this message]
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=49e22913-cbe4-4aad-8882-39dd014fbf87@u69g2000hse.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).