From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: enhanced select-safe-coding-system
Date: Fri, 03 May 2002 10:54:30 +0300 [thread overview]
Message-ID: <6137-Fri03May2002105430+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <rzqg01a2mve.fsf@djlvig.dl.ac.uk> (message from Dave Love on 02 May 2002 23:41:57 +0100)
> From: Dave Love <d.love@dl.ac.uk>
> Date: 02 May 2002 23:41:57 +0100
>
> "Eli Zaretskii" <eliz@is.elta.co.il> writes:
>
> > Shouldn't we disallow saving a file whose coding: says something
> > different from the actual encoding? Is there any situation when such
> > a file means anything but trouble when it is visited?
>
> Yes, but anyhow it surely can't be right absolutely to prevent users
> saving files.
That's true, there's a dilemma here. I believe Stefan was saying
something similar.
Perhaps we should think about rewriting `coding:', or maybe removing
it, after asking for confirmation.
> `coding:' tags aren't the only thing `set-auto-coding' can note.
Sorry, I'm afraid I don't follow; could you please elaborate?
next prev parent reply other threads:[~2002-05-03 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqk7qp2log.fsf@djlvig.dl.ac.uk>
2002-05-01 7:14 ` enhanced select-safe-coding-system Richard Stallman
2002-05-01 16:27 ` Eli Zaretskii
2002-05-01 18:51 ` Stefan Monnier
2002-05-02 22:16 ` Richard Stallman
2002-05-02 22:41 ` Dave Love
2002-05-03 7:54 ` Eli Zaretskii [this message]
2002-05-04 23:01 ` Dave Love
2002-05-02 22:39 ` Dave Love
2002-05-03 13:27 ` Stefan Monnier
2002-05-04 3:36 ` Richard Stallman
2002-05-05 23:06 ` Stefan Monnier
2002-05-04 22:56 ` Dave Love
2002-05-05 23:24 ` Stefan Monnier
2002-05-08 22:17 ` Dave Love
2002-05-14 19:41 ` Richard Stallman
2002-05-14 19:52 ` Stefan Monnier
2002-05-16 7:21 ` Richard Stallman
2002-05-04 3:36 ` Richard Stallman
2002-05-04 23:11 ` Dave Love
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6137-Fri03May2002105430+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.