all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Another strange bug suggestion: inserting in wrong buffer when some screen related resources are scare (w32)
Date: Mon, 07 Mar 2011 22:01:39 -0500	[thread overview]
Message-ID: <jwv39myl3ov.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTimm6+KbOu+iWnL=B7A=J6rSepv3pFeEPZE_AmVv@mail.gmail.com> (Lennart Borgman's message of "Tue, 8 Mar 2011 00:58:12 +0100")

> I just saw that Emacs was inserting text in the wrong buffer. This
> seems related to running out of GDI objects.

I guess it's marginally better than "Emacs doesn't work", but it's still
pretty useless as a bug description.

> I have suggested before that Emacs should always check return values
> from system calls. I am suggesting it again since it might catch a
> problem like this. (And again: I would add more of them to my patched
> version of Emacs if I had time to keep the patches, but I don't have
> that.)

If you send your patches in clean manageable patches, we might be able
to incorporate them.  Tho of course, if they're not high enough on
people's list of priorities, they may linger for a long time.  But since
you can commit them yourself, all you need is for someone to approve it,
which is easier: the key is to make the patch short enough that it can
be reviewed with no effort.


        Stefan



      reply	other threads:[~2011-03-08  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 23:58 Another strange bug suggestion: inserting in wrong buffer when some screen related resources are scare (w32) Lennart Borgman
2011-03-08  3:01 ` Stefan Monnier [this message]

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=jwv39myl3ov.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.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 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.