hexl-find-file doesn't know read-only

hexl-find-file doesn't know read-only

[Dan Jacobson]

hexl-find-file does not notice that a file is read-only on the disk
making the new buffer read-write.  Plus I see it uses
find-file-literally, who's docs say not to use it in lisp programs.

By the way, why must Flyspell and Fill get turned on for me when I'm
hexl-find-file'ing? All I do in .emacs is
(setq default-major-mode 'text-mode)
(add-hook 'text-mode-hook (lambda ()
   (flyspell-mode 1)
   (turn-on-auto-fill)))

By the way, it bugs me that hexl's C-e, hexl-end-of-line, gets the
cursor to two columns earlier than the end of line. If I want to copy
and paste that line, C-@ C-e ESC w, I must use the mouse instead.
-- 
http://jidanni.org/ Taiwan(04)25854780

these little RMS fixes filling up my mailbox

[Dan Jacobson]

>>>>> "RMS" == Richard Stallman <rms@gnu.org> mails:

RMS> Does this replacement function fix it?
RMS> (defun hexl-find-file (filename)...

While not exactly zonked out on 'ludes, often I don't get around to
testing these little RMS fixes filling up my mailbox.

I suppose they still get into the official emacs, even though one
doesn't see the diff jazz.

You are spoiling all my fun if I have to like stop in my tracks and
review past issues.  There was a bug and you said you were
sorry. There, case closed. Next bug. Without pets to abuse, it's the
best I can do for jollies.

Re: these little RMS fixes filling up my mailbox

[Kim F. Storm]

Dan Jacobson <jidanni@dman.ddts.net> writes:

> >>>>> "RMS" == Richard Stallman <rms@gnu.org> mails:
> 
> RMS> Does this replacement function fix it?
> RMS> (defun hexl-find-file (filename)...
> 
> While not exactly zonked out on 'ludes, often I don't get around to
> testing these little RMS fixes filling up my mailbox.

Hi Dan,

If you report bugs or suggest features, you should be prepared to
use the efforts necessary to test the fixes or features when RMS
(or others) has spend time on the issue.

Since you were the one to see the bug in the first place, or
the person to propose a new feature, who better than you can
judge whether the bug is actually fixed [in your setup], or
an added feature really matches what you proposed.

> 
> I suppose they still get into the official emacs, even though one
> doesn't see the diff jazz.
> 
You cannot always assume that!

> You are spoiling all my fun if I have to like stop in my tracks and
> review past issues.  There was a bug and you said you were
> sorry. There, case closed. Next bug. Without pets to abuse, it's the
> best I can do for jollies.

Too bad.  Maybe you should write in your bug reports, that you do not
want to test a fix, so that we at least don't waste our time sending
the fix to you.

-- 
Kim F. Storm  http://www.cua.dk

Re: these little RMS fixes filling up my mailbox

[Thien-Thi Nguyen]

no-spam@cua.dk (Kim F. Storm) writes:

   Dan Jacobson <jidanni@dman.ddts.net> writes:

   > I suppose they still get into the official emacs, even
   > though one doesn't see the diff jazz.

   You cannot always assume that!

more to the point, the purpose of asking "does this [...] fix
that?"  is to receive confirmation on the validity of the fix,
so that it can indeed go into the repo.  furthermore,
confirmation raises confidence in the thought process of the bug
fixer, which has positive repercussions later.  likewise, the
answer "no" alerts the bug fixer to perhaps try a different
approach, the end result again being refinement of thought.

it's no surprise that education systems of aspiring totalitarian
regimes downplay the scientific method; GNU collaborators and
cultivators have no need for such self-restrictions, however.

thi

Re: these little RMS fixes filling up my mailbox

[Eli Zaretskii]

> From: Dan Jacobson <jidanni@dman.ddts.net>
> Date: Wed, 12 Mar 2003 05:35:00 +0800
> 
> You are spoiling all my fun if I have to like stop in my tracks and
> review past issues.  There was a bug and you said you were
> sorry. There, case closed. Next bug.

No.  We still depend on your input to close the bug.  If you don't say
that the bug is fixed by the patch, there might be no way for us to
verify that the patch fixes it.