unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: w32-pass-rwindow-to-system
Date: Wed, 21 Jan 2009 23:12:05 +0100	[thread overview]
Message-ID: <e01d8a50901211412h7fda004fjbbdcb35571a48248@mail.gmail.com> (raw)
In-Reply-To: <49772C9A.8020300@gnu.org>

On Wed, Jan 21, 2009 at 3:09 PM, Jason Rumney <jasonr@gnu.org> wrote:
> Lennart Borgman wrote:
>>
>> At the moment I do not have time to dig out that part. I have spent
>> quite a lot of time trying to get this fix into Emacs, but the
>> resistance has been too strong for the limited time I have so I have
>> run out of time for this. (Feel free to grab the patch from my
>> patches.)
>>
>
> You have never once made the effort to separate out the bugfixes from your
> extensive patch that modifies a number of unrelated aspects of Emacs
> behaviour. Are you surprised that there is resistance when we always get
> told "take it all or sort through it yourself"?

I looked through what I wrote and maybe you are right, see this thread:

  http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01604.html

As you can see in this last message there where quite a few things fixed there.

I am not sure how to proceed. I think it all should go in one parcel.
You may of course have comments on my coding style etc. Feel free to
comment on that.

Since this has been in use for 3 y now I think it could be considered
rather stable.

The best way to get the patch now is from the patch I upload for
Emacs+EmacsW32. It is the files

  src/w32fns.c
  src/w32menu.c
  src/w32term.h
  w32-meta.el (new, not in the patch)

The latest patch is from 2009-01-15. The patches are here

  http://ourcomments.org/Emacs/DL/EmacsW32/src/




  parent reply	other threads:[~2009-01-21 22:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  1:57 w32-pass-rwindow-to-system MON KEY
2009-01-21  9:29 ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21  9:48   ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21  9:55     ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 10:12       ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 10:26         ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 10:59           ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 11:11             ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 14:09             ` w32-pass-rwindow-to-system Jason Rumney
2009-01-21 14:20               ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 22:12               ` Lennart Borgman [this message]
2009-01-21 14:23     ` w32-pass-rwindow-to-system Jason Rumney
2009-01-21 18:29       ` w32-pass-rwindow-to-system MON KEY
2009-01-21 21:58       ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 23:03         ` w32-pass-rwindow-to-system MON KEY
2009-01-21 23:14           ` w32-pass-rwindow-to-system Lennart Borgman
  -- strict thread matches above, loose matches on Subject: below --
2009-01-21 13:05 w32-pass-rwindow-to-system grischka
2009-01-21 14:19 ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 15:41   ` w32-pass-rwindow-to-system grischka

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=e01d8a50901211412h7fda004fjbbdcb35571a48248@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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 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).