CORRUPTED MESSAGE
This is the Courier Mail Server 0.45 on repository.lp.se.
I received the following message for delivery to your address. This message contains several internal formatting errors. This is often caused by viruses that attempt to infect remote systems. Instead of blocking this message, it has been converted as a safe, text-only attachment that can be safely read with a text editor.
This sometimes also happens when the sender's mail software has a bug that creates improperly-formatted messages. Although these kinds of formatting errors may often be ignored by other mail servers, this server detects and intercepts improperly-coded messages in order to prevent viruses from taking advantage of bugs in E-mail programs:
----------------------------------------------------------------------------- This message contains improperly-formatted binary content, or attachment.
See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> for more information. -----------------------------------------------------------------------------
Received: from localhost (localhost [127.0.0.1]) (uid 33) by repository.lp.se with local; Wed, 09 Jun 2004 11:17:25 +0200 Subject: [repository.lp.se #18] Bug with workspace context From: "Dan Lilliehorn via RT" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Precedence: bulk X-RT-Loop-Prevention: repository.lp.se RT-Ticket: repository.lp.se #18 Managed-by: RT 3.0.10 (http://www.bestpractical.com/rt/) RT-Originator: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 09 Jun 2004 11:17:25 +0200
And again after logging in. Bah. > [guest - Wed Jun 09 11:14:28 2004]: > > State changed to resolved. > > > [guest - Wed Jun 09 08:28:02 2004]: > > > > Should be solved by the split of virtual screen init i tag > ctwm-3_7-alpha5. > > > > > > > [levitte - Sun Mar 02 08:16:37 2003]: > > > > > > 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. > > > > > > > > > > > > > > >
