xemacs

2007-10-23 Thread Ronald Smith 
I have cygwin installed on my XP machine along with the x-server and the
Singular version of xemacs.
 
I am trying to get my scroll wheel to work with xemacs, but I simply
cannot get it to work.
 
I entered the following into my $HOME/.xemacs file:
 
$ more ~/.xemacs
;;===
;;scroll on  mouse wheel
;;===
(global-set-key 'button5 'scroll-up-one)
(global-set-key 'button4 'scroll-down-one)
(global-set-key '(control button5) 'scroll-up)
(global-set-key '(control button4) 'scroll-down)
$

But xemacs does not recognize the commands.  However if I go to the menu
"Cmds->Evaluate List Expression..." And enter each command individually,
it works just fine.

Obviously I'm doing something wrong that is very basic but I'm danged if
I can figure out what it is.

My home directory is located in /cygdrive/c/Documents and Settings/user
which has embedded spaces in the name.  The imbedded spaces cause other
issues, is this what is the problem?

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: xterm not accepting Window Title name changes

2007-10-23 Thread Mark J. Reed 
Somewhat OT, but don't you need -e on the echo command to get it to
interpret the backslash escapes?  Or is that only needed for the
non-numeric ones?


On 10/23/07, Paul McFerrin <[EMAIL PROTECTED]> wrote:
> Hi:
>
> I can't seem to get xterm to recognize Window Title name changes via the
> following:
>
> echo "\0332;new_title\07\c"
>
> I have added the following new lines to my .Xdefaults file with no effect.
>
> XTerm.AllowTitleOps:true
> XTerm.AllowTitleOps: true
> XTerm.allowTitleOps: true
> XTerm.allowWindowOps:true
> XTerm.AllowWindowOps:true
> XTerm.vt100.AllowTitleOps:  true
> XTerm.vt100.AllowTitleOps:   true
> XTerm.vt100.allowTitleOps:   true
> XTerm.vt100.allowWindowOps:  true
> XTerm.vt100.AllowWindowOps:  true
> VT100.AllowTitleOps: true
> VT100.allowTitleOps: true
> VT100.allowWindowOps:true
> VT100.AllowWindowOps:true
> XTerm.vt100.utf8Title:   true
> VT100.AllowTitleOps:true
>
> and I have modified my "startxwin.sh script to start xterm the following
> way:
>
> xterm -aw -b 5 +cm -rw -sb -sk  -sl 1500 -rv -e /usr/bin/ksh -l &
>
> I thought it was working yesterday, but at this point I can't remember
> very much!  Yesterday, I only had the:
>
>XTerm.AllowTitleOps:true
>
> line in .Xdefaults and I thought it was working
>
> What am I doing wrong??
>
>
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://x.cygwin.com/docs/
> FAQ:   http://x.cygwin.com/docs/faq/
>
>


-- 
Mark J. Reed <[EMAIL PROTECTED]>

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: xterm not accepting Window Title name changes

2007-10-23 Thread Paul McFerrin 
Problem solved.  There was an apparent race condition between the start 
of the XWin server and the startup of the xterm command.  Just by adding 
a 2 second sleep after starting XWin, I have no problem being able to 
set the window title thru an escape sequence.


Guess that is what you get for having a super-fast machine.  :)
Paul McFerrin wrote:  
I can't seem to get xterm to recognize Window Title name changes via 
the

following:

echo "\0332;new_title\07\c"




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: XWin Multiwindow fails to start

2007-10-23 Thread Nick Douma 
On Mon, Oct 22, 2007 at 06:28:33PM +0200, Nick Douma wrote:
> On Mon, Oct 22, 2007 at 05:11:12PM +0200, Holger Krull wrote:
> > Nick Douma schrieb:
> > > No one who has any suggestions... ?
> > 
> > Not for your main problem. Just the general idea that sometimes deleting 
> > and reinstalling helps to solve strange problems. 
> I'll try that tomorrow

I have deleted my previous installation of Cygwin, and reinstalled all the 
required CygwinX packages, along with 
openssh, pico and svn.

When I use the startx script, it seems to startup fine, but at the end I get 
this error: 

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:Can't find file "pc/us_intl" for symbols include
>   Exiting
>   Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from 
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from 
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from 
list!
winPointerWarpCursor - Discarding first warp: 640 512
winInitMultiWindowWM - pthread_mutex_lock () returned.
winProcEstablishConnection - Hello
winProcEstablishConnection - Clipboard is not enabled, returning.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
cat: /cygdrive/x/.Xauthority: No such file or directory

winMultiWindowXMsgProcIOErrorHandler!

  8 [unknown (0x7B8)] X 1144 _cygtls::handle_exceptions: Error while 
dumping state (probably corrupted 
stack)
xinit:  connection to X server lost.
xterm:  fatal IO error 104 (Connection reset by peer) or KillClient on X server 
":0.0"

Also, seemingly totally random, Xterm may or may not start up and work. But I 
can't make any other programs 
connect to the X server, nor can I use remote X11 forwarding to this PC.
 

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: xterm not accepting Window Title name changes

2007-10-23 Thread Jay Abel 
Found this somewhere along the way, I forgot where.  Works on my
machine.  I did notice that the cd command on my machine does meddle
with the prompt string and send it to xterm.  Sorry I can't be more
helpful.

#!/usr/bin/perl
#
# This is a simple program to change the text in an X-windows title bar.
# This used to be a shell script, but that got hosed in an ``update''
# on Linux.  It's probably a Good Idea(tm) to do this in perl anyway since
# the my program could be vulnerable to somebody putting something really
# wierd in as arguments.
#
print qq(\033]2;@ARGV\007);
exit(0)


On 10/22/07, Paul McFerrin <[EMAIL PROTECTED]> wrote:
>
> Hum...  The PS1 setting. Nope, that's not the problem.
>
> The root of the settitle() function is NOT the setting of PS1.  It's
> setting in /etc/profile is commented out.  In my local .profile, PS1 is
> set to just '$PWD'.  I have verified that there are no other hidden
> settings of PS1.
>
> I tried your settitle() function, and the title remains unchanged:
> basename of the shell.
>
> My posting in the archives envolves the use of 'rxvt' only and has
> nothing to do with xterm.  I always startup 'startxwin.sh' from a
> non-rxvt window (e.g. the console window).
>
> Regardless what shell I'm using, it always seems to get it's basename
> into the window.  Hum
>
> Does anyone else want to try a stab at this problem?
>
> Brian Dessent wrote:
> > Paul McFerrin wrote:
> >
> >
> >> I can't seem to get xterm to recognize Window Title name changes via the
> >> following:
> >>
> >> echo "\0332;new_title\07\c"
> >>
> >
> > You were just recently posting in the thread where this came up before:
> >  and
> > .  Specifically, the
> > default Cygwin prompt (PS1) contains characters that set the title so
> > anything you do that doesn't involve changing PS1 will have no effect --
> > or more precisely, your echo command above does set the title for a few
> > milliseconds, until the next prompt overwrites it.   (In your rxvt
> > example, you aren't starting a login shell and thus /etc/profile isn't
> > sourced and PS1 isn't set, which is presumably why it works there.)
> >
> > Brian
> >
> > --
> > Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> > Problem reports:   http://cygwin.com/problems.html
> > Documentation: http://x.cygwin.com/docs/
> > FAQ:   http://x.cygwin.com/docs/faq/
> >
> >
>
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://x.cygwin.com/docs/
> FAQ:   http://x.cygwin.com/docs/faq/
>
>

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/