unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Kurn <kurn@sfu.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10072@debbugs.gnu.org
Subject: bug#10072: 23.3; invisible text
Date: Mon, 21 Nov 2011 03:12:27 -0800	[thread overview]
Message-ID: <20111121111227.GA11214@sfu.ca> (raw)
In-Reply-To: <5376D105CD20484990AAB55C158138B0@us.oracle.com>

On Sun 20 Nov 2011 16:27 -0800, Drew Adams wrote:
> 
> > > Fundamentally it's a bug, and I generally don't like to 
> > > document bugs.
> > 
> > On this point I disagree with you very strongly.  It's much /more/
> > important to document bugs than any other aspect of the code.  I have
> > told several students this from time to time, and, like you, they
> > tend to resist the idea.
> > 
> > I gather that there is no great push on to remedy this behavior,
> > so this bug may hang around for some time . . .
> 
> FWIW - Bugs, other known problems, and workarounds are typically *not*
> documented as part of the technical doc itself.  One reason for this is that the
> doc is meant to describe what the product does, or rather, what it should do,
> what it is supposed to do.  In a way, the doc is like a spec that the product is
> meant to reflect.
> 


Ah, another voice, and also an intelligent one.  It's gratifying to
meet the interesting community of Emacs-developers.  I do so much
of my coding on my own . . .

Anyhow, I'd say I'm still in disagreement about this with you.  However,
I'm pleased with the way the proposed wording is written (as you'll see
in the next message), so I'd say the issue is resolved.

Andrew






  reply	other threads:[~2011-11-21 11:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 19:14 bug#10072: 23.3; invisible text Andrew Kurn
2011-11-20  4:57 ` Stefan Monnier
2011-11-20 10:24   ` Andrew Kurn
2011-11-20 20:30     ` Stefan Monnier
2011-11-21  0:03       ` Andrew Kurn
2011-11-21  0:27         ` Drew Adams
2011-11-21 11:12           ` Andrew Kurn [this message]
2011-11-21  2:27         ` Stefan Monnier
2011-11-21 11:37           ` Andrew Kurn

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=20111121111227.GA11214@sfu.ca \
    --to=kurn@sfu.ca \
    --cc=10072@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).