On Mon, 8 Apr 2013, Russell Johnson wrote:
> Is that really supposed to be xmodpam instead of xmodmap?
Nope. Dyslectic fingers.
Rich
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Apr 8, 2013, at 2:23 PM, Rich Shepard wrote:
> xmodpam .Xmodmap
Is that really supposed to be xmodpam instead of xmodmap?
Russell Johnson
r...@dimstar.net
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/
On Mon, 8 Apr 2013, Rogan Creswick wrote:
> I wonder if your .xinitrc is actually in use.
Shrug. I dunno.
> Are you using startx to start the X server?
Yep. It's an alias for startxfce4.
> I ask because the last line appears to be starting Window Maker, while you
> later refer to XFCE; i
Thanks! Comments in-line below.
On Mon, Apr 8, 2013 at 2:23 PM, Rich Shepard wrote:
>Here it is:
>
> #!/bin/sh
> # $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
>
>
>
> # Start the window manager:
> exec /usr/bin/wmaker $NOCPP
>
>
>There ain't no error text. X is invoked
On Mon, 8 Apr 2013, Rogan Creswick wrote:
> Would you mind posting / sending the whole script?
Rogan,
Here it is:
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodm
On Mon, Apr 8, 2013 at 1:56 PM, Rich Shepard wrote:
> On Mon, 8 Apr 2013, Rogan Creswick wrote:
>
> > Could you post the content of your .xinitrc, and the specific errors that
> > you're seeing? It would also help to know the path to xmodmap (`which
> > xmodmap` should provide that).
>
> Rogan,
>
On Mon, 8 Apr 2013, Rogan Creswick wrote:
> It would also help to know the path to xmodmap (`which xmodmap` should
> provide that).
Oops! Forgot to mention it's in /usr/bin/ where it's always been.
Rich
___
PLUG mailing list
PLUG@lists.pdxlinux.org
On Mon, 8 Apr 2013, Rogan Creswick wrote:
> Could you post the content of your .xinitrc, and the specific errors that
> you're seeing? It would also help to know the path to xmodmap (`which
> xmodmap` should provide that).
Rogan,
It's the default Slackware .xinitrc. The error I see is that it
On Mon, Apr 8, 2013 at 10:16 AM, Rich Shepard wrote:
> On Mon, 8 Apr 2013, Dale Snell wrote:
>
> > The only thing that comes to me is that you no longer have the
> > xmodmap(1) command installed.
>
> Dale,
>
>That's not the issue. xmodmap is present and accounted for. I can run
> 'xmodmap .Xmo
On Mon, 8 Apr 2013, Dale Snell wrote:
> The only thing that comes to me is that you no longer have the
> xmodmap(1) command installed.
Dale,
That's not the issue. xmodmap is present and accounted for. I can run
'xmodmap .Xmodmap' from the command line and it works. For whatever reason,
the sa
On Mon, 8 Apr 2013 08:34:21 -0700 (PDT)
Rich Shepard wrote:
>I recently upgraded my Dell Latitude from Slackware-13.37/x86_64 to
> -14.0/x86_64 and now .Xmodmap tells me that the commands cannot be
> found. This same file is used to switch the caplock and ctrl keys. It
> works on other hosts
I recently upgraded my Dell Latitude from Slackware-13.37/x86_64 to
-14.0/x86_64 and now .Xmodmap tells me that the commands cannot be found.
This same file is used to switch the caplock and ctrl keys. It works on
other hosts and worked on the Dell before now. It does not run when
~/.xinitrc is
On Sun, Apr 7, 2013 at 5:06 PM, John Jason Jordan wrote:
> On Sun, 7 Apr 2013 16:31:01 -0700
> Matt McKenzie dijo:
>
> >Is something going to be done about the spam on PLUG-JOBS?
> >That's all the traffic I have seen on that list since the move to the
> >new server.
> >I think it is a good resour
13 matches
Mail list logo