CORRUPTED MESSAGE

This is the Courier Mail Server 0.39 on cvs.lp.se.

I received the following message for delivery to your address.  Unfortunately,
the sender's mail software did not properly format the following message
according to Internet mail formatting protocols, and I can only deliver mail
which has been properly formatted according to Internet standards.  Instead
of returning the following message as undeliverable, it is saved, in its
original form, in the following attachment, which you can open with any
editor or word processor.

Please notify the original sender that their message was not properly
formatted by their mail software.  The specific mail protocol error in the
original message is as follows:

-----------------------------------------------------------------------------
The following message contains 8-bit content, but does not have the required
MIME headers for 8-bit data transport.

See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> for more information.
-----------------------------------------------------------------------------
Received: from localhost (localhost [127.0.0.1])
  (uid 1)
  by cvs.lp.se with local; Sun, 02 Mar 2003 08:16:39 +0100
X-RT-Loop-Prevention: cvs.lp.se
Message-Id: <[EMAIL PROTECTED]>
Subject: [cvs.lp.se #18] Bug with workspace context
In-Reply-To: <[EMAIL PROTECTED]>
Managed-BY: RT 2.0.14 (http://bestpractical.com/rt/)
From: "Richard Levitte via RT" <[EMAIL PROTECTED]>
RT-Ticket: cvs.lp.se #18
X-Mailer: Perl5 Mail::Internet v1.56
Reply-To: [EMAIL PROTECTED]
Precedence: bulk
RT-Originator: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sender: daemon <[EMAIL PROTECTED]>
Date: Sun, 02 Mar 2003 08:16:39 +0100


Bj�rn says:

bjorn> Well, the simple answer is that if you bind a key in the workspace
bjorn> context, it becomes dead in all other contexts:
bjorn>
bjorn> "a" = : workspace : f.beep
bjorn>
bjorn> would make the "a" key generate a beep in the workspace context, as
bjorn> expected. But it would mean "a" could not be used in Emacs, your XTerm
bjorn> or any other program. Obviously, this is not what you'd expect or want.
bjorn>
bjorn> Notice also that this is *not* the behavior you get if you apply my
bjorn> patch to 3.6, so something else has changed.
[...]
bjorn> Well, I expect that binding a key in the workspace context should not
bjorn> render it useless everywhere else. Something has changed since 3.6 and
bjorn> I can't figure out exactly what from the changelog. The changes you
bjorn> say Claude has made does not show up in the changelog, and looking at
bjorn> some of the files, event.c for one, there are significant changes.
bjorn>
bjorn> For example, the test I made for:
bjorn>
bjorn> Tmp_win == Scr->workSpaceMgr.workspaceWindow.twm_win
bjorn>
bjorn> is made in other places in the original code. Looking at 3.7alpha4,
bjorn> some have been changed to a test for:
bjorn>
bjorn> Tmp_win->wspmgr
bjorn>
bjorn> others to:
bjorn>
bjorn> Tmp_win == Scr->currentvs->wsw->twm_win
bjorn>
bjorn> I don't understand exactly what has changed, so I can't comment on
bjorn> why, but it *could* be related to the Xinerama-patches.

--
Richard Levitte     | http://richard.levitte.org/ | Spannv. 38, I
Levitte Programming | http://www.lp.se/           | S-168 35 Bromma
T: +46-708-26 53 44 |                             | SWEDEN
     "Price, performance, quality...  choose the two you like"

Reply via email to