Re: mc, xterm-clear, Ctrl-O and Home/End dilemma
Hi, On 22.12.2017 00:38, Marek Zarychta wrote: Maybe switching to the x-window driven desktop environment at home should be taken into consideration in this case. Both ncures and slang versions of misc/mc work fine (key bindings, border drawing etc.) for ssh(1) client called from xterm capable terminal. Yup, when I work from FreeBSD on Xorg, everything is fine, but not from putty. Eugene. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mc, xterm-clear, Ctrl-O and Home/End dilemma
Hi,
On 21.12.2017 23:20, Eugene M. Zheganin wrote:
Hi,
So, there's a puzzle of minor issues and I wanted to ask how you guys
deal with it.
- with standard ncurses misc/mc there's no borders in mc in putty, and
Ctrl-O flushes the output beneath panels.
-with slang misc/mc Ctrl-O flushes the output beneath panels (and I
lived with this through years, but then discovered xterm-clear).
- with slang and xterm-clear Home/End doesn't work in putty.
everything else is fine, but this hurts.
I use my FreeBSD desktop at work and from home wvia putty, so I really
want to solve this without learning keays each time (and it seems like
they aren't save on "Save setup".
Ideas ?
So, I figured it out, thanks to https://midnight-commander.org/ticket/2633
two things should be done on each FreeBSD mc is ran on to not ruin other
ssh sessions:
- a wrapper that will reside in PATH earlier than mc binary:
#!/bin/sh
#
# simple knob to fix mc Ctrl-O without ruining remote Linux sshs
#
if [ $TERM = "xterm" ]; then {
TERM=xterm-clear
} fi
/usr/local/bin/mc $*
- a fix to /usr/local/share/mc/mc.lib:
[terminal:xterm-clear]
copy=xterm
Then everything works, remote ssh sessions are not affected (like
Linuxes/other OSes that don't have xterm-clear), putty works fine,
Home/End working fine.
Eugene.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mc, xterm-clear, Ctrl-O and Home/End dilemma
## Eugene M. Zheganin (e...@norma.perm.ru): > I use my FreeBSD desktop at work and from home wvia putty, so I really > want to solve this without learning keays each time (and it seems like > they aren't save on "Save setup". Putty has quite a bunch of options to configure terminal behaviour, and you can make it send different terminal identifiers (from your description, I'm not sure where you switched terminal modes). Maybe fiddling with putty or the terminal identifier will help? Termcap even has a putty entry... I'm not a putty user myself (I prefer xterm and openssh), so I can only guess. Regards, Christoph -- Spare Space ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mc, xterm-clear, Ctrl-O and Home/End dilemma
On Thu, Dec 21, 2017 at 11:20:35PM +0500, Eugene M. Zheganin wrote: > Hi, > > So, there's a puzzle of minor issues and I wanted to ask how you guys > deal with it. > > - with standard ncurses misc/mc there's no borders in mc in putty, and > Ctrl-O flushes the output beneath panels. > > -with slang misc/mc Ctrl-O flushes the output beneath panels (and I > lived with this through years, but then discovered xterm-clear). > > - with slang and xterm-clear Home/End doesn't work in putty. everything > else is fine, but this hurts. > > I use my FreeBSD desktop at work and from home wvia putty, so I really > want to solve this without learning keays each time (and it seems like > they aren't save on "Save setup". > > Ideas ? > > Maybe switching to the x-window driven desktop environment at home should be taken into consideration in this case. Both ncures and slang versions of misc/mc work fine (key bindings, border drawing etc.) for ssh(1) client called from xterm capable terminal. -- Marek Zarychta signature.asc Description: PGP signature
mc, xterm-clear, Ctrl-O and Home/End dilemma
Hi, So, there's a puzzle of minor issues and I wanted to ask how you guys deal with it. - with standard ncurses misc/mc there's no borders in mc in putty, and Ctrl-O flushes the output beneath panels. -with slang misc/mc Ctrl-O flushes the output beneath panels (and I lived with this through years, but then discovered xterm-clear). - with slang and xterm-clear Home/End doesn't work in putty. everything else is fine, but this hurts. I use my FreeBSD desktop at work and from home wvia putty, so I really want to solve this without learning keays each time (and it seems like they aren't save on "Save setup". Ideas ? Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xterm - truetype fonts and missing underscore
On 08/25/11 01:43, Mark Saad wrote: What else is in you .Xresources file. I removed it entirely and problem remains. Also have you tried using xft formated font names. Ie xft:luxi mono:size=10 ? xterm -fa 'xft:luxi mono:size=10' produces an xterm which display correctly xterm -fa 'xft:Monospace:size=10' produces an xterm that displays incorrectly. The linkVolodymyr Kostyrko explains the problem. cheers -- Tony Maheremail: tonyma...@optusnet.com.au ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xterm - truetype fonts and missing underscore
On 08/25/11 01:27, Volodymyr Kostyrko wrote: 24.08.2011 12:01, Tony Maher wrote: Hello, recently (not sure exactly when) my xterms no longer showed the underscore character. In my .Xresources I had (and have had this setting for years): XTerm*faceName: Monospace XTerm*faceSize: 10 I noticed when experimenting and modifying values that for one choice the bottom part of letters like 'g' was missing. So changed faceSize to 11 and all is good. In gnome-terminal with Monospace/10 font underscores showed up fine (and was ok in gnome font selector). So it appears to be xterm specific. Has anyone else experienced this? +1 from me http://lists.nongnu.org/archive/html/freetype/2011-08/msg00020.html Ok. Thanks for the link. cheers -- Tony Maheremail: tonyma...@optusnet.com.au ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xterm - truetype fonts and missing underscore
Tony What else is in you .Xresources file . Also have you tried using xft formated font names . Ie xft:luxi mono:size=10 ? -- Mark Saad Mark.saad@longcount.orgOn Aug 24, 2011 7:08 AM, Tony Maher <tonyma...@optusnet.com.au> wrote: Hello, recently (not sure exactly when) my xterms no longer showed the underscore character. In my .Xresources I had (and have had this setting for years): XTerm*faceName: Monospace XTerm*faceSize: 10 I noticed when experimenting and modifying values that for one choice the bottom part of letters like 'g' was missing. So changed faceSize to 11 and all is good. In gnome-terminal with Monospace/10 font underscores showed up fine (and was ok in gnome font selector). So it appears to be xterm specific. Has anyone else experienced this? cheers -- Tony Maheremail: tonyma...@optusnet.com.au ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xterm - truetype fonts and missing underscore
24.08.2011 12:01, Tony Maher wrote: Hello, recently (not sure exactly when) my xterms no longer showed the underscore character. In my .Xresources I had (and have had this setting for years): XTerm*faceName: Monospace XTerm*faceSize: 10 I noticed when experimenting and modifying values that for one choice the bottom part of letters like 'g' was missing. So changed faceSize to 11 and all is good. In gnome-terminal with Monospace/10 font underscores showed up fine (and was ok in gnome font selector). So it appears to be xterm specific. Has anyone else experienced this? +1 from me http://lists.nongnu.org/archive/html/freetype/2011-08/msg00020.html -- Sphinx of black quartz judge my vow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
xterm - truetype fonts and missing underscore
Hello, recently (not sure exactly when) my xterms no longer showed the underscore character. In my .Xresources I had (and have had this setting for years): XTerm*faceName: Monospace XTerm*faceSize: 10 I noticed when experimenting and modifying values that for one choice the bottom part of letters like 'g' was missing. So changed faceSize to 11 and all is good. In gnome-terminal with Monospace/10 font underscores showed up fine (and was ok in gnome font selector). So it appears to be xterm specific. Has anyone else experienced this? cheers -- Tony Maheremail: tonyma...@optusnet.com.au ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Low CPU Freq responsible for xterm pixel corruption on RELENG_7
On Sun, Jan 27, 2008 at 08:54:00PM -0500, J.R. Oldroyd wrote: > Some weeks ago, I posted on the x11@ list of a problem of pixel corruption > I am seeing in xterm windows. An example of the problem can still be > seen here: > http://opal.com/jr/xterm-corruption.gif > Quick summary: Wide xterm windows (wider than 158 columns, 1440 pixels) > have the problem shown, but only when at least that many columns are on > the screen. That is, moving a wide window so that it is partially off > the screen causes the corruption to cease when less than 158 columns > are displayed. (trimmin thr Cc list) as a matter of fact i have been seeing the same problem also on RELENG_6, on a desktop PC without powerd, and using an Intel chipset with integrated video (i945 chipset) and the I810 driver: X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 I seem to remember my laptop (Dell X300, i915 video card) also has similar problems with wide xterms. I believe the problem is in the i810 driver, or some interaction with the system (agpgart) rather than related to powerd and CPU freq. cheers luigi > Further investigation has unearthed that this problem happens only when > the CPU frequency is set to low levels, which was happening because of > powerd. When the CPU frequency is set low, these pixel corruptions happen. > When the CPU freq is raised they do not: everything is normal. > > Disabling powerd and manually adjusting the CPU frequency gives these results: > > # sysctl dev.cpu.0.freq_levels > dev.cpu.0.freq_levels: 3176/-1 2779/-1 2382/-1 1985/-1 1588/-1 1191/-1 794/-1 > 397/-1 > > CPU freq from 3176 to 1191 causes no problems. > CPU freq at 794 or 397 causes pixel corruptions. > > This problem did not happen on RELENG_6. > > -jr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Low CPU Freq responsible for xterm pixel corruption on RELENG_7
Some weeks ago, I posted on the x11@ list of a problem of pixel corruption I am seeing in xterm windows. An example of the problem can still be seen here: http://opal.com/jr/xterm-corruption.gif Quick summary: Wide xterm windows (wider than 158 columns, 1440 pixels) have the problem shown, but only when at least that many columns are on the screen. That is, moving a wide window so that it is partially off the screen causes the corruption to cease when less than 158 columns are displayed. Further investigation has unearthed that this problem happens only when the CPU frequency is set to low levels, which was happening because of powerd. When the CPU frequency is set low, these pixel corruptions happen. When the CPU freq is raised they do not: everything is normal. Disabling powerd and manually adjusting the CPU frequency gives these results: # sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 3176/-1 2779/-1 2382/-1 1985/-1 1588/-1 1191/-1 794/-1 397/-1 CPU freq from 3176 to 1191 causes no problems. CPU freq at 794 or 397 causes pixel corruptions. This problem did not happen on RELENG_6. -jr signature.asc Description: PGP signature
Re: xorg-clients conflicts with xterm (patch)
On Wed, Nov 23, 2005 at 12:47:13PM +1100, Mark Andrews wrote:
>
> >
> > > $ sh
> > > $ PACKAGES=/home/packages
> > > $ export PACKAGES
> > > $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> > > pkg_info: can't find package 'xorg-clients-6.8.2' installed or in a file!
> > > $ PKG_PATH=/home/packages/All
> > > $ export PKG_PATH
> > > $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> > > xorg-clients-6.8.2 X client programs and related files from X.Org
> > > $
> >
> > We need to clean PKG_PATH from the envirionment when looking
> > for conflicts.
> >
> > e.g.
> >
> > found=`${SETENV} PKG_PATH= ${PKG_INFO} -I ${CONFLICTS:C/.+/'&'/} 2>/dev/
> > null | ${AWK} '{print $$1}'`;
> >
> > Mark
>
> While we are fixing things the man page for pkg_info needs to be updated.
> PKG_PATH is not mentioned. It's hard to debug problems without the required
> information.
That's true. I'll update pkg_info(1) soon.
-Kirill
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
>
> > $ sh
> > $ PACKAGES=/home/packages
> > $ export PACKAGES
> > $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> > pkg_info: can't find package 'xorg-clients-6.8.2' installed or in a file!
> > $ PKG_PATH=/home/packages/All
> > $ export PKG_PATH
> > $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> > xorg-clients-6.8.2 X client programs and related files from X.Org
> > $
>
> We need to clean PKG_PATH from the envirionment when looking
> for conflicts.
>
> e.g.
>
> found=`${SETENV} PKG_PATH= ${PKG_INFO} -I ${CONFLICTS:C/.+/'&'/} 2>/dev/
> null | ${AWK} '{print $$1}'`;
>
> Mark
While we are fixing things the man page for pkg_info needs to be updated.
PKG_PATH is not mentioned. It's hard to debug problems without the required
information.
ENVIRONMENT
BLOCKSIZE If the environment variable BLOCKSIZE is set the block counts
will be displayed in units of that size block.
PKG_TMPDIR Points to the directory where pkg_info creates its temporary
files. If this variable is not set, TMPDIR is used. If both
are unset, the builtin defaults are used.
PKG_DBDIR Specifies an alternative location for the installed package
database.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> $ sh
> $ PACKAGES=/home/packages
> $ export PACKAGES
> $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> pkg_info: can't find package 'xorg-clients-6.8.2' installed or in a file!
> $ PKG_PATH=/home/packages/All
> $ export PKG_PATH
> $ /usr/local/sbin/pkg_info -I xorg-clients-6.8.2
> xorg-clients-6.8.2 X client programs and related files from X.Org
> $
We need to clean PKG_PATH from the envirionment when looking
for conflicts.
e.g.
found=`${SETENV} PKG_PATH= ${PKG_INFO} -I ${CONFLICTS:C/.+/'&'/} 2>/dev/
null | ${AWK} '{print $$1}'`;
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
>
> > On Wednesday 23 of November 2005 01:11, Joel Hatton wrote:
> > > > Joel Hatton wrote:
> > > > > What was the rationale behind changing this behaviour for 206_1?
> > > >
> > > > That xterm should install as xterm and not xterm-static.
> > >
> > > This is certainly sensible, however it appears that the onus has now been
> > > put on the maintainer of xorg-clients to change its installation process
> > > to accommodate xterm.
> >
> > It has been accommodated.
> >
> > > This hasn't happened yet (after cvsup this morning),
> > > which means that xterm remains incompatible with the current xorg-clients
> > > version and thus will fail during every portupgrade -a until then, unless
> > > I make xterm a held package.
> > >
> > > According to UPDATING, upgrading "xorg-clients to 6.8.2_1 or newer" is ok
> ,
> > > but this is not the case:
> > >
> > > # pkg_info -I xorg-clients\*
> > > xorg-clients-6.8.2_1 X client programs and related files from X.Org
> > >
> > > # portupgrade -p xterm
> > >
> > > ... (building)
> > >
> > > ---> Installing the new version via the port
> > > ===> Installing for xterm-206_1
> > >
> > > ===> xterm-206_1 conflicts with installed package(s):
> > > xorg-clients-6.8.2
> > >
> > > They install files into the same place.
> > > Please remove them first with pkg_delete(1).
> >
> > Interesting. This is how it goes here:
> >
> > # pkg_info -I xorg-clients\*
> > xorg-clients-6.8.2_1 X client programs and related files from X.Org
> >
> > # portupgrade -fp xterm
> > ...
> > ===> Building for xterm-206_1
> > ... (build) ...
> > ===> Installing for xterm-206_1
> > ... (install) ...
> > ===> Registering installation for xterm-206_1
> > ...
> >
> >
> > Can you try without portupgrade (cd /usr/ports/x11/xterm && make install).
> >
> > > Couldn't this transition have been better managed?
> >
> > Possibly. Do you have a suggestion so it can be used in similar future
> > situations?
> >
> >
> > Dejan
> > ___
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> For some reason the conflict detection code comes out with
> xorg-clients-6.8.2 even though when you run the steps by hand
> they don't produce xorg-clients-6.8.2.
>
> After modifying Mk/bsd.port.mk to display what it is doing:
>
> ===> Installing for xterm-206_1
> set -x ; found=`/usr/local/sbin/pkg_info -I 'xorg-clients-6.7*' 'xorg-client
> s-6.8.[0-1]*' 'xorg-clients-6.8.2' 'XFree86-clients-4.[0-4]*' 'XFree86-client
> s-4.5.0' 'XFree86-3*' 2>/dev/null | /usr/bin/awk '{print $1}'`; conflicts_wi
> th=; echo found is ${found}; for entry in ${found}; do prfx=`/usr/local/sb
> in/pkg_info -q -p "${entry}" 2> /dev/null | /usr/bin/sed -ne '1s/[EMAIL
> PROTECTED] //p'`;
> orgn=`/usr/local/sbin/pkg_info -q -o "${entry}" 2> /dev/null`; if [ "//usr
> /X11R6" = "/${prfx}" -a "/x11/xterm" != "/${orgn}" ]; then conflicts_with="$
> {conflicts_with} ${entry}"; fi; done; if [ -n "${conflicts_with}" ]; then
> echo; echo "===> xterm-206_1 conflicts with installed package(s): "; for
> entry in ${conflicts_with}; do echo " ${entry}"; done; echo; echo "
> They install files into the same place."; echo " Please remove the
> m first with pkg_delete(1)."; exit 1; fi
> + /usr/local/sbin/pkg_info+ /usr/bin/awk -I {print $1} xorg-clients-6.7*
> xorg-clients-6.8.[0-1]* xorg-clients-6.8.2 XFree86-clients-4.[0-4]* XFree86-
> clients-4.5.0 XFree86-3*
> + found=xorg-clients-6.8.2
> + conflicts_with=
> + echo found is xorg-clients-6.8.2
> found is xorg-clients-6.8.2
> + /usr/local/sbin/pkg_info+ /usr/bin/sed -q -ne -p 1s/[EMAIL PROTECTED] //p
> xorg-clients-
> 6.8.2
>
> + prfx=/usr/X11R6
> + /usr/local/sbin/pkg_info -q -o xorg-clients-6.8.2
> + orgn=x11/xorg-clients
> + [ //usr/X11R6 = //usr/X11R6 -a /x11/xterm != /x11/xorg-clients ]
> + conflicts_with= xorg-clients-6.8.2
> + [ -n xorg-clients-6.8.2 ]
> + echo
>
> + echo ===> xterm-206_1 c
Re: xorg-clients conflicts with xterm (patch)
> On Wednesday 23 of November 2005 01:11, Joel Hatton wrote:
> > > Joel Hatton wrote:
> > > > What was the rationale behind changing this behaviour for 206_1?
> > >
> > > That xterm should install as xterm and not xterm-static.
> >
> > This is certainly sensible, however it appears that the onus has now been
> > put on the maintainer of xorg-clients to change its installation process
> > to accommodate xterm.
>
> It has been accommodated.
>
> > This hasn't happened yet (after cvsup this morning),
> > which means that xterm remains incompatible with the current xorg-clients
> > version and thus will fail during every portupgrade -a until then, unless
> > I make xterm a held package.
> >
> > According to UPDATING, upgrading "xorg-clients to 6.8.2_1 or newer" is ok,
> > but this is not the case:
> >
> > # pkg_info -I xorg-clients\*
> > xorg-clients-6.8.2_1 X client programs and related files from X.Org
> >
> > # portupgrade -p xterm
> >
> > ... (building)
> >
> > ---> Installing the new version via the port
> > ===> Installing for xterm-206_1
> >
> > ===> xterm-206_1 conflicts with installed package(s):
> > xorg-clients-6.8.2
> >
> > They install files into the same place.
> > Please remove them first with pkg_delete(1).
>
> Interesting. This is how it goes here:
>
> # pkg_info -I xorg-clients\*
> xorg-clients-6.8.2_1 X client programs and related files from X.Org
>
> # portupgrade -fp xterm
> ...
> ===> Building for xterm-206_1
> ... (build) ...
> ===> Installing for xterm-206_1
> ... (install) ...
> ===> Registering installation for xterm-206_1
> ...
>
>
> Can you try without portupgrade (cd /usr/ports/x11/xterm && make install).
>
> > Couldn't this transition have been better managed?
>
> Possibly. Do you have a suggestion so it can be used in similar future
> situations?
>
>
> Dejan
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
For some reason the conflict detection code comes out with
xorg-clients-6.8.2 even though when you run the steps by hand
they don't produce xorg-clients-6.8.2.
After modifying Mk/bsd.port.mk to display what it is doing:
===> Installing for xterm-206_1
set -x ; found=`/usr/local/sbin/pkg_info -I 'xorg-clients-6.7*'
'xorg-clients-6.8.[0-1]*' 'xorg-clients-6.8.2' 'XFree86-clients-4.[0-4]*'
'XFree86-clients-4.5.0' 'XFree86-3*' 2>/dev/null | /usr/bin/awk '{print $1}'`;
conflicts_with=; echo found is ${found}; for entry in ${found}; do
prfx=`/usr/local/sbin/pkg_info -q -p "${entry}" 2> /dev/null | /usr/bin/sed -ne
'1s/[EMAIL PROTECTED] //p'`; orgn=`/usr/local/sbin/pkg_info -q -o "${entry}"
2> /dev/null`; if [ "//usr/X11R6" = "/${prfx}" -a "/x11/xterm" != "/${orgn}"
]; then conflicts_with="${conflicts_with} ${entry}"; fi; done; if [ -n
"${conflicts_with}" ]; then echo; echo "===> xterm-206_1 conflicts with
installed package(s): "; for entry in ${conflicts_with}; do echo "
${entry}"; done; echo; echo " They install files into the same place.";
echo " Please remove them first with pkg_delete(1)."; exit 1; fi
+ /usr/local/sbin/pkg_info+ /usr/bin/awk -I {print $1} xorg-clients-6.7*
xorg-clients-6.8.[0-1]* xorg-clients-6.8.2 XFree86-clients-4.[0-4]*
XFree86-clients-4.5.0 XFree86-3*
+ found=xorg-clients-6.8.2
+ conflicts_with=
+ echo found is xorg-clients-6.8.2
found is xorg-clients-6.8.2
+ /usr/local/sbin/pkg_info+ /usr/bin/sed -q -ne -p 1s/[EMAIL PROTECTED] //p
xorg-clients-6.8.2
+ prfx=/usr/X11R6
+ /usr/local/sbin/pkg_info -q -o xorg-clients-6.8.2
+ orgn=x11/xorg-clients
+ [ //usr/X11R6 = //usr/X11R6 -a /x11/xterm != /x11/xorg-clients ]
+ conflicts_with= xorg-clients-6.8.2
+ [ -n xorg-clients-6.8.2 ]
+ echo
+ echo ===> xterm-206_1 conflicts with installed package(s):
===> xterm-206_1 conflicts with installed package(s):
+ echo xorg-clients-6.8.2
xorg-clients-6.8.2
+ echo
+ echo They install files into the same place.
They install files into the same place.
+ echo Please remove them first with pkg_delete(1).
Please remove them first with pkg_delete(1).
+ exit 1
*** Error code 1
Stop in /usr/ports/x11/xterm.
*** Error code 1
Stop in /usr/ports/x11/xterm.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade79
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 23 of November 2005 01:11, Joel Hatton wrote: [snip] > # pkg_info -I xorg-clients\* > xorg-clients-6.8.2_1 X client programs and related files from X.Org > > # portupgrade -p xterm > > ... (building) > > ---> Installing the new version via the port > ===> Installing for xterm-206_1 > > ===> xterm-206_1 conflicts with installed package(s): > xorg-clients-6.8.2 What is the output of /usr/sbin/pkg_info -I 'xorg-clients-6.7*' 'xorg-clients-6.8.[0-1]*' 'xorg-clients-6.8.2' 'XFree86-clients-4.[0-4]*' 'XFree86-clients-4.5.0' 'XFree86-3*' ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 23 of November 2005 01:11, Joel Hatton wrote: > > Joel Hatton wrote: > > > What was the rationale behind changing this behaviour for 206_1? > > > > That xterm should install as xterm and not xterm-static. > > This is certainly sensible, however it appears that the onus has now been > put on the maintainer of xorg-clients to change its installation process > to accommodate xterm. It has been accommodated. > This hasn't happened yet (after cvsup this morning), > which means that xterm remains incompatible with the current xorg-clients > version and thus will fail during every portupgrade -a until then, unless > I make xterm a held package. > > According to UPDATING, upgrading "xorg-clients to 6.8.2_1 or newer" is ok, > but this is not the case: > > # pkg_info -I xorg-clients\* > xorg-clients-6.8.2_1 X client programs and related files from X.Org > > # portupgrade -p xterm > > ... (building) > > ---> Installing the new version via the port > ===> Installing for xterm-206_1 > > ===> xterm-206_1 conflicts with installed package(s): > xorg-clients-6.8.2 > > They install files into the same place. > Please remove them first with pkg_delete(1). Interesting. This is how it goes here: # pkg_info -I xorg-clients\* xorg-clients-6.8.2_1 X client programs and related files from X.Org # portupgrade -fp xterm ... ===> Building for xterm-206_1 ... (build) ... ===> Installing for xterm-206_1 ... (install) ... ===> Registering installation for xterm-206_1 ... Can you try without portupgrade (cd /usr/ports/x11/xterm && make install). > Couldn't this transition have been better managed? Possibly. Do you have a suggestion so it can be used in similar future situations? Dejan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> Joel Hatton wrote: > > What was the rationale behind changing this behaviour for 206_1? > > That xterm should install as xterm and not xterm-static. This is certainly sensible, however it appears that the onus has now been put on the maintainer of xorg-clients to change its installation process to accommodate xterm. This hasn't happened yet (after cvsup this morning), which means that xterm remains incompatible with the current xorg-clients version and thus will fail during every portupgrade -a until then, unless I make xterm a held package. According to UPDATING, upgrading "xorg-clients to 6.8.2_1 or newer" is ok, but this is not the case: # pkg_info -I xorg-clients\* xorg-clients-6.8.2_1 X client programs and related files from X.Org # portupgrade -p xterm ... (building) ---> Installing the new version via the port ===> Installing for xterm-206_1 ===> xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). Couldn't this transition have been better managed? cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
Joel Hatton wrote: > What was the rationale behind changing this behaviour for 206_1? That xterm should install as xterm and not xterm-static. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> > xterm-206_1 Terminal emulator for the X Window System > xorg-clients-6.8.2_1 X client programs and related files from X.Org > > then, portupgrade -fp xterm xorg-clients > ... > ===> Installing for xterm-206_1 > > ===> xterm-206_1 conflicts with installed package(s): > xorg-clients-6.8.2 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > On this note, I generated the same error trying to install xterm-206_1 _after_ deinstalling xorg-clients-6.8.2_1. >From Updating: 20051113: AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients AUTHOR: [EMAIL PROTECTED] Xterm no longer installs with '-static' prefix. Users should upgrade XFree86-clients to 4.5.0_1 or xorg-clients to 6.8.2_1 or newer before attempting upgrade of xterm to 206_1 or newer. Previous versions remove xterm on deinstall so CONFLICTS have been set accordingly. What was the rationale behind changing this behaviour for 206_1? cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
Argh! Correction below. On Thursday 17 November 2005 00:02, Andy Fawcett wrote: > On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote: > > On Wednesday 16 of November 2005 04:26, James Long wrote: > > > After hours of head-banging over the past couple of days, > > > I have finally succeeded in installing EITHER > > > xorg-clients-6.8.2_1 OR xterm-206_1. Previously, > > > installing either port told me that it conflicted > > > with the other, in spite of having cvsupped my > > > ports tree twice to ensure I was getting the most > > > recent version of the ports, hopefully including a > > > fix to the chicken-and-egg problem noted in > > > /usr/ports/UPDATING > > > > x11/xorg-clients port does not conflict with any version of xterm. > > Where do you see that? > > For an interesting variation, I have a totally up to date ports tree, > with the latest versions of xterm and xorg-clients already installed: > > xterm-206_1 Terminal emulator for the X Window System > xorg-clients-6.8.2_1 X client programs and related files from X.Org > > then, portupgrade -fp xterm xorg-clients > ... > ===> Installing for xterm-206_1 > > ===> xterm-206_1 conflicts with installed package(s): > xorg-clients-6.8.2 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > Again, please note that xterm conflicts with the version of the > clients it is supposed to work with. this should read "shows a conflict with a version of the port that is not installed". > This is repeatable on 2 systems > I have tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64. > > A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote: > On Wednesday 16 of November 2005 04:26, James Long wrote: > > After hours of head-banging over the past couple of days, > > I have finally succeeded in installing EITHER > > xorg-clients-6.8.2_1 OR xterm-206_1. Previously, > > installing either port told me that it conflicted > > with the other, in spite of having cvsupped my > > ports tree twice to ensure I was getting the most > > recent version of the ports, hopefully including a > > fix to the chicken-and-egg problem noted in > > /usr/ports/UPDATING > > x11/xorg-clients port does not conflict with any version of xterm. > Where do you see that? For an interesting variation, I have a totally up to date ports tree, with the latest versions of xterm and xorg-clients already installed: xterm-206_1 Terminal emulator for the X Window System xorg-clients-6.8.2_1 X client programs and related files from X.Org then, portupgrade -fp xterm xorg-clients ... ===> Installing for xterm-206_1 ===> xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Again, please note that xterm conflicts with the version of the clients it is supposed to work with. This is repeatable on 2 systems I have tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 16 of November 2005 04:26, James Long wrote:
> After hours of head-banging over the past couple of days,
> I have finally succeeded in installing EITHER
> xorg-clients-6.8.2_1 OR xterm-206_1. Previously,
> installing either port told me that it conflicted
> with the other, in spite of having cvsupped my
> ports tree twice to ensure I was getting the most
> recent version of the ports, hopefully including a
> fix to the chicken-and-egg problem noted in
> /usr/ports/UPDATING
x11/xorg-clients port does not conflict with any version of xterm. Where do
you see that?
> Once I spotted an odd bit of output in the portupgrade
> dialogue, I made a change to xorg-clients Makefile
> which allowed everything to install. pkgdb -F afterwards
> and all my dependencies are tidied up.
>
> May I suggest the following patch to
> /usr/ports/x11/xorg-clients/Makefile:
>
>
> --- Makefile Sun Nov 13 21:47:34 2005
> +++ foo Tue Nov 15 19:19:37 2005
> @@ -18,7 +18,7 @@
> MAINTAINER= [EMAIL PROTECTED]
> COMMENT= X client programs and related files from X.Org
>
> -RUN_DEPENDS= xterm>0:${PORTSDIR}/x11/xterm
> +RUN_DEPENDS= xterm:${PORTSDIR}/x11/xterm
> LIB_DEPENDS= png.5:${PORTSDIR}/graphics/png \
> Xft.2:${PORTSDIR}/x11-fonts/libXft
Versions of x11/xterm port prior to xterm-206_1 do not install 'xterm'
executable. The above would cause xorg-clients port to try to install xterm
even if xterm-206 (for example) is alredy installed which would then fail.
Dejan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
Andy Fraser wrote: On Wednesday 16 Nov 2005 3:26 am, James Long wrote: After hours of head-banging over the past couple of days, I have finally succeeded in installing EITHER xorg-clients-6.8.2_1 OR xterm-206_1. Previously, installing either port told me that it conflicted with the other, in spite of having cvsupped my ports tree twice to ensure I was getting the most recent version of the ports, hopefully including a fix to the chicken-and-egg problem noted in /usr/ports/UPDATING I had a similar problem. xterm-206_1 conflicted with xorg-clients-6.8.2_1. portmanager suggested removing xorg-clients after which xterm installed but xorg-clients wouldn't build anymore[1]. Some Googling suggested that the nVidia driver port (I don't know whether you're using this or not) replaced glx.h causing the xorg-clients to fail (unchecked) and reinstalling xorg-libraries would fix it. This worked for me. I'm not sure whether you're having the same problem or not but I thought I'd mention this just in case. [1] I also had this problem with 5.4-STABLE but to get around it there I installed a binary package to save time. I reinstalled the xorg-libraries but keep on getting the sale error above sincerely Filippo Moretti ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 16 Nov 2005 3:26 am, James Long wrote: > After hours of head-banging over the past couple of days, > I have finally succeeded in installing EITHER > xorg-clients-6.8.2_1 OR xterm-206_1. Previously, > installing either port told me that it conflicted > with the other, in spite of having cvsupped my > ports tree twice to ensure I was getting the most > recent version of the ports, hopefully including a > fix to the chicken-and-egg problem noted in > /usr/ports/UPDATING I had a similar problem. xterm-206_1 conflicted with xorg-clients-6.8.2_1. portmanager suggested removing xorg-clients after which xterm installed but xorg-clients wouldn't build anymore[1]. Some Googling suggested that the nVidia driver port (I don't know whether you're using this or not) replaced glx.h causing the xorg-clients to fail (unchecked) and reinstalling xorg-libraries would fix it. This worked for me. I'm not sure whether you're having the same problem or not but I thought I'd mention this just in case. [1] I also had this problem with 5.4-STABLE but to get around it there I installed a binary package to save time. -- Andy Fraser. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Tue, Nov 15, 2005 at 07:56:33PM -0800, David Wolfskill wrote:
> On Tue, Nov 15, 2005 at 07:49:10PM -0800, James Long wrote:
> >
> > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found
> >
> > and investigated the Makefile to find why the odd package
> > name of "xterm>0".
>
> Looks as if the thing to do would have been to run "pkgdb -F" and delete
> that dependency.
Again, at that time, xorg-clients was not installed, thus
that dependency was not in the package database. Notice
that the portupgrade output with that "xterm>0" line is
a "portupgrade -N" invocation, to install a new port, not
to upgrade an existing port. I always welcome and try to
learn from corrections, but I can't see that pkgdb -F would
be able to remove a dependency for a port that is not (yet)
installed.
That dependency is actually verbatim in the Makefile, I quote:
RUN_DEPENDS=xterm>0:${PORTSDIR}/x11/xterm
Hence my patch. Or if the above syntax is correct, perhaps
someone can point me towards an explanation of the syntax found
in that RUN_DEPENDS= line for my edification. Once I removed
the ">0" from the Makefile, and since portupgrade had already
built (but failed to install) xorg-clients, I was able to
simply "make install" in the xorg-clients ports directory,
and all the previously-built stuff got installed, along
with xterm-206_1.
I'm just asking someone (my original post cc'ed $MAINTAINER)
to review the accuracy of that RUN_DEPENDS line. portupgrade
certainly seems to parse the ">0" as part of the port name,
rather than as some sort of conditional operator.
Regards,
Jim
>
> Peace,
> david
> --
> David H. Wolfskill[EMAIL PROTECTED]
> Prediction is difficult, especially if it involves the future. -- Niels Bohr
>
> See http://www.catwhisker.org/~david/publickey.gpg for public key.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> Date: Tue, 15 Nov 2005 20:44:25 -0800 (PST)
> From: Rob <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> James Long wrote:
> >
> > Then I noticed:
> >
> > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found
> >
> > and investigated the Makefile to find why the odd package
> > name of "xterm>0".
>
> My portstree from Nov. 12th, has this at this particular place:
>
> RUN_DEPENDS=xterm-static:${PORTSDIR}/x11/xterm
> LIB_DEPENDS=png.5:${PORTSDIR}/graphics/png \
> Xft.2:${PORTSDIR}/x11-fonts/libXft
>
>
> Is this "xterm>0" line a broken download with cvsup, or something?
Nope! It's that way in CVS.
I got xterm-206_1 to install by deleting xorg-clients and then
installing xterm-206_1 followed by xorg-clisents-6.8.2_1. It has worked
fine on all 5 systems I have done it on to this point.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
James Long wrote:
>
> Then I noticed:
>
> ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found
>
> and investigated the Makefile to find why the odd package
> name of "xterm>0".
My portstree from Nov. 12th, has this at this particular place:
RUN_DEPENDS=xterm-static:${PORTSDIR}/x11/xterm
LIB_DEPENDS=png.5:${PORTSDIR}/graphics/png \
Xft.2:${PORTSDIR}/x11-fonts/libXft
Is this "xterm>0" line a broken download with cvsup, or something?
Rob.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Tue, Nov 15, 2005 at 07:32:45PM -0800, David Wolfskill wrote: > On Tue, Nov 15, 2005 at 07:26:16PM -0800, James Long wrote: > > After hours of head-banging over the past couple of days, > > I have finally succeeded in installing EITHER > > xorg-clients-6.8.2_1 OR xterm-206_1. Previously, > > installing either port told me that it conflicted > > with the other, in spite of having cvsupped my > > ports tree twice to ensure I was getting the most > > recent version of the ports, hopefully including a > > fix to the chicken-and-egg problem noted in > > /usr/ports/UPDATING > > It mentioned a conflict; I don't recall a chicken-and-egg issue. Forgive me for not including enough background. Due to an improper procedure on my part in converting from XFree86 to Xorg, plus a complete rebuild of all ports as part of upgrading to 6.0-STABLE, and a bit of ignorance on my part, I wound up in a situation where I had pkg_deleted both xorg-clients and xterm. I was then in a situation where I couldn't install xorg-clients because it depended on xterm, but xterm couldn't be installed because it con- flicted with xorg-clients. That was my chicken-and-egg dilemma. pkgdb -F was dutifully showing several packages with dangling dependencies to those two, but I couldn't install either of them. cvsupping to the most recent ports tree didn't change the problem. Then I noticed: ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found and investigated the Makefile to find why the odd package name of "xterm>0". I then patched the Makefile as I posted, and I was able to "make install" in xorg-clients and pkgdb -F and everything installed. Further documentation of the state of my pkg_info and dependencies is below. Jim [pkg_info | egrep "xorg|xterm" # note lack of xorg-clients and xterm] t21 : 19:04:41 /root# pkg_info | egrep "xorg|xterm" xorg-6.8.2 X.Org distribution metaport xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts xorg-fonts-cyrillic-6.8.2 X.Org Cyrillic bitmap fonts xorg-fonts-encodings-6.8.2 X.Org font encoding files xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.8.2 X.Org TrueType fonts xorg-fonts-type1-6.8.2 X.Org Type1 fonts xorg-fontserver-6.8.2 X font server from X.Org xorg-libraries-6.8.2 X11 libraries and headers from X.Org xorg-manpages-6.8.2 X.Org library manual pages xorg-nestserver-6.8.2 Nesting X server from X.Org xorg-printserver-6.8.2_2 X Print server from X.Org xorg-server-6.8.2_6 X.Org X server and related programs xorg-vfbserver-6.8.2 X virtual framebuffer server from X.Org [Initial state of ports dependencies:] [EMAIL PROTECTED] pkgdb -F ---> Checking the package registry database Stale dependency: kde-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): xorg-vfbserver-6.8.2 (score:27%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kde-3.4.2 -> xterm-205_1 (x11/xterm): New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kdeadmin-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdeadmin-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdebase-3.4.2_2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdebase-3.4.2_2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdegames-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdegames-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdelibs-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdelibs-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-akode-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-akode-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdetoys-3.4.2 -> xterm-205_1 (x11/xterm): Skip th
xorg-clients conflicts with xterm (patch)
After hours of head-banging over the past couple of days,
I have finally succeeded in installing EITHER
xorg-clients-6.8.2_1 OR xterm-206_1. Previously,
installing either port told me that it conflicted
with the other, in spite of having cvsupped my
ports tree twice to ensure I was getting the most
recent version of the ports, hopefully including a
fix to the chicken-and-egg problem noted in
/usr/ports/UPDATING
Once I spotted an odd bit of output in the portupgrade
dialogue, I made a change to xorg-clients Makefile
which allowed everything to install. pkgdb -F afterwards
and all my dependencies are tidied up.
May I suggest the following patch to
/usr/ports/x11/xorg-clients/Makefile:
--- MakefileSun Nov 13 21:47:34 2005
+++ foo Tue Nov 15 19:19:37 2005
@@ -18,7 +18,7 @@
MAINTAINER=[EMAIL PROTECTED]
COMMENT= X client programs and related files from X.Org
-RUN_DEPENDS= xterm>0:${PORTSDIR}/x11/xterm
+RUN_DEPENDS= xterm:${PORTSDIR}/x11/xterm
LIB_DEPENDS= png.5:${PORTSDIR}/graphics/png \
Xft.2:${PORTSDIR}/x11-fonts/libXft
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: erase2 ( xterm
I'm cc-ing questions@ in the hope that Vance gets an
answer, and because this probably isn't really stable@
material.
*To whom it may concern: **Please** remove the
freebd-stable CC if you reply.
Torfinn Ingolfsen wrote:
On Tue, 30 Nov 2004 08:12:28 -0500
Vance Shipley <[EMAIL PROTECTED]> wrote:
What's up with the ( key functioning as a backspace key
in an xterm?
It doesn't do that here:
[EMAIL PROTECTED] echo $TERM
xterm
[EMAIL PROTECTED] stty -a | grep erase
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
eol2 = ; erase = ^H; erase2 = ^H; intr = ^C; kill = ^U;
status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;
I'm running:
[EMAIL PROTECTED] uname -a
FreeBSD kg-work.kg4.no 5.3-STABLE FreeBSD 5.3-STABLE #1: Sun Nov 14
20:19:11 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G
i386
Hmm, note that he was grepping "erase2" and you grepped "erase."
Check the original post
It shows up like Vance's here, in xterm, Eterm, Aterm,
gnometerminal, and on the console on ttyv2 whether $TERM
is set to "xterm-color", "xterm", or "cons25". Probably if you grep
the same term, yours will say that also ...
However, his statement "functioning as a backspace" doesn't
ring true, because, no such functionality is present (for me) in
any terminal with that key, regardless of the $TERM variable.
Terminal emulation is a little bit mysterious to me; maybe someone
with more expertise can answer the larger question. I'm just curious
whether pushing the {right parenthesis} character on Vance's
keyboard actually does backspace, and whether he's on the console,
on X, using PuTTY from a Winboxen, etc., and/or what terminal emulator
he's actually using, what version he's running, whether his termcap
symlink or file is corrupt/missing, etc., etc., blah, blah
Vance?
Kevin Kinsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: erase2 ( xterm
On Tue, 30 Nov 2004 08:12:28 -0500 Vance Shipley <[EMAIL PROTECTED]> wrote: > > What's up with the ( key functioning as a backspace key > in an xterm? It doesn't do that here: [EMAIL PROTECTED] echo $TERM xterm [EMAIL PROTECTED] stty -a | grep erase -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo eol2 = ; erase = ^H; erase2 = ^H; intr = ^C; kill = ^U; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; I'm running: [EMAIL PROTECTED] uname -a FreeBSD kg-work.kg4.no 5.3-STABLE FreeBSD 5.3-STABLE #1: Sun Nov 14 20:19:11 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G i386 -- Regards, Torfinn Ingolfsen, Norway ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
erase2 ( xterm
What's up with the ( key functioning as a backspace key in an xterm? $ stty -a | grep erase2 eol2 = ; erase = ^?; erase2 = (; intr = ^C; kill = ^U; I tried setting ttyModes to no avail. -Vance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bug in xterm?
- Forwarded message from Andy Farkas <[EMAIL PROTECTED]> -
>--
>>$ perl -mDigest::MD5 -e 'print pack("H*",Digest::MD5::md5("test"))' >ert
>>$ wc ert
>> 0 1 8 ert
>>$ hexdump -C ert
>> 9f 4d f1 3c ae 73 67 46 |.M.<.sgF|
>>0008
>>$ cat ert
>>
>>At this point it hangs; sending ^Q doesn't help. But if you press cursor-up
>>a few times it comes back to life.
...
>
>Oddly, a real vt220 would do the same thing, but neither has any use for
>the content of the string.
A real VT220 does NOT hang. It prints "Mnhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bug in xterm?
On Sat, Nov 27, 2004 at 11:52:15AM +1100, Edwin Groothuis wrote:
> [~] [EMAIL PROTECTED]>perl -mDigest::MD5 -e 'print
> pack("H*",Digest::MD5::md5("test"))' | hexdump -C
> 9f 4d f1 3c ae 73 67 46 |.M.<.sgF|
>
> This shows that it outputs some high-ascii data, which causes the
> xterm to stop output. If you do "echo hi > /tmp/aaa" while in this
> state (be alert for typos), you see that it still accepts commands,
> but doesn't show them anymore.
Thanks. I got a nice analysis off-list:
--
>$ perl -mDigest::MD5 -e 'print pack("H*",Digest::MD5::md5("test"))' >ert
>$ wc ert
> 0 1 8 ert
>$ hexdump -C ert
> 9f 4d f1 3c ae 73 67 46 |.M.<.sgF|
>0008
>$ cat ert
>
>At this point it hangs; sending ^Q doesn't help. But if you press cursor-up
>a few times it comes back to life.
>
>It must be a strange escape sequence if typing characters and hitting Return
>lots of times is not enough to bring it back to life. I suppose it's
>technically not an escape sequence, since it doesn't include 0x1B :-)
0x9f is APC - which begins a string. Technically it's only terminated by
a ST (0x9c or ESC followed by backslash), but xterm also accepts a BEL,
which may be what's emitted when you do a few uparrows (getting an error
response from the shell). There's also a resource setting to work around
some Linux junk (hardcoded applications with malformed sequences) that
can make it terminate on a carriage return. But generally, it would look
as if it's hung.
(A soft-reset would fix the problem with less damage to your session).
Oddly, a real vt220 would do the same thing, but neither has any use for
the content of the string.
--
I guess I wasn't expecting any escape sequence which consumed an infinite
number of characters - and presumably also, Konsole implements a different
terminal emulation (or implements vt220 wrongly).
Cheers,
Brian.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bug in xterm?
On Fri, Nov 26, 2004 at 02:07:51PM +, Brian Candler wrote:
> I can cause xterm to hang reliably with the following command:
>
> perl -mDigest::MD5 -e 'print pack("H*",Digest::MD5::md5("test"))'
>
> A control-middlebutton-"Do Full Reset" is needed to get out of this state.
It's not a bug in xterm on itself. If you cat a binary file you
might end up in the same situation.
[~] [EMAIL PROTECTED]>perl -mDigest::MD5 -e 'print
pack("H*",Digest::MD5::md5("test"))' | hexdump -C
9f 4d f1 3c ae 73 67 46 |.M.<.sgF|
This shows that it outputs some high-ascii data, which causes the
xterm to stop output. If you do "echo hi > /tmp/aaa" while in this
state (be alert for typos), you see that it still accepts commands,
but doesn't show them anymore.
In other words, don't worry too much about it but make sure you
redirect binary output to files or pipes and not the console.
Edwin
--
Edwin Groothuis |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bug in xterm?
I can cause xterm to hang reliably with the following command:
perl -mDigest::MD5 -e 'print pack("H*",Digest::MD5::md5("test"))'
A control-middlebutton-"Do Full Reset" is needed to get out of this state.
Konsole doesn't have this problem (but Konsole takes too much screen
real-estate). Anyway, just thought it was worth a mention...
Regards,
Brian.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree 4.3.0 update : xterm won't comeup
pirat <[EMAIL PROTECTED]> writes: > i have just finished upgrade my small machine to 4.8rc with xfree86 to 4.3.0 > my window manager is blackbox-0.65 and here is my uname -a > once in blackbox, i hardly get xterm popped up for me, as a plain > user. i have no idea up to now. I encountered this as well. Fired up xterm from a command line (within Emacs, which did work still) and it couldn't load some library, possibly libXft.so.1 ? IIRC libXft.so.2 did exist but that's not what xterm was looking for. I also had "rxvt" installed (from ports) and that worked fine so I used that to su and rebuild X11, first the server, then the clients, from ports. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: xterm title sequence affects icon name too
On Thu, 23 May 2002 12:12, Hanspeter Roth wrote: > On May 20 at 16:29, Hanspeter Roth spoke: > > Some versions (configurations?) of Xterm can be sent 2;...\007 > > to change the title only. And 0;...\007 is used to change both > > the title and icon name. > > But in certain installations (configurations?) 2;...\007 which > > is expected to change only the title also changes the icon name. > > What does it depend on? Are there different versions of Xterms? > > This seems to be an issue of the window manager Icewm 1.0.8, rather > than of xterm. > Under an alternative window manager Twm xterm behaves as expected. > I'm using Icewm 1.0.8. An 1.0.7 installation behaves also as > expected. You might want to bring this up with the developers of icewm then, since this dosn't relate to FreeBSD-stable. - James -- James Pole - www.jamespole.cjb.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XTERM
John Merryweather Cooper <[EMAIL PROTECTED]> types: > "Robert T.G. Tan" wrote: > > I tried /etc/ttys: > > > > ttyv5 "/usr/X11R6/bin/xdm -nodaemon" xterm-color on secure > > > > but I didn't get the xterm-color value for TERM. You need to log out of the X session, then hup init for that to take effect. You may need to do it in the other order, or shut down xdm a second time after hupping init to get the change through everything looking at it. > I by-pass the X resource stuff (which I haven't quite figured out) and > use the following in my .shrc X resource stuff is one of the biggest problems with X. It makes the Windows Registry look sane. The X resource to set is xtermName. If you have a .Xresources and it gets loaded, that's probably the best place to put this. You'll need to reload .Xresources with xrdb for it to take effect. That way, xterm will get the information from the X server, so that xterms started on other systems displaying on yours will also get xterm-color. If you don't want to do that, you can either put it in your .Xdefaults or whatever XENVIRONMENT points to, or in a directory pointed to by XAPPRLESDIR or XUSERFILESEARCHPATH if you use one of those. > # adjust TERM to color xterm under X > # use linux Java under X > if [ $TERM = "xterm" ]; then > TERM=xterm-color; export TERM > JAVA_HOME=/usr/local/linux-jdk1.3.0; export JAVA_HOME > fi TERM should already be in the environment, so the export is redundant. I did it that way for a year or so before moving it into .Xresources. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XTERM
"Robert T.G. Tan" wrote: > > I tried /etc/ttys: > > ttyv5 "/usr/X11R6/bin/xdm -nodaemon" xterm-color on secure > > but I didn't get the xterm-color value for TERM. > > Also looked for some resource that would define the TERM value, but > couldn't find it.. > > tnx, rotan. > > Robert T.G. Tan([EMAIL PROTECTED])@2001.04.22 12:40:46 +: > > Where does TERM get set, if not in ~/.*rc, or /etc/whatever-default-configs > > I by-pass the X resource stuff (which I haven't quite figured out) and use the following in my .shrc # for non-X sessions use Java 1.1.8 JAVA_HOME=/usr/local/jdk1.1.8; export JAVA_HOME # adjust TERM to color xterm under X # use linux Java under X if [ $TERM = "xterm" ]; then TERM=xterm-color; export TERM JAVA_HOME=/usr/local/linux-jdk1.3.0; export JAVA_HOME fi # add appropriate java to path JAVA_PATH=$JAVA_HOME/bin PATH=$JAVA_PATH:$PATH; export PATH This allows me to do two things: 1) display color directory listings in Gnome-Term, rxvt, and/or eterm; and 2) switch my java from 1.1.8 to the linux-1.3.0 for all my X sessions (so that Star Office works somewhat better). jmc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: My xterm has broken :(
On Mon, Jan 15, 2001 at 07:11:24PM +, Catch-all m-box wrote: > Hi, > Can anyone help with this one? > > I have STABLE from this afternoon, but have also upgraded to XFree86 4 > It seems to be okay, except when I try to get an xterm, I get nothing! > > This is the log message generated: > /usr/libexec/ld-elf.so.1: Undefined symbol "_XA_UTF8_STRING" referenced from COP > Y relocation in xterm I have also seen that on my machine. What i have done: fetched XFree 4.02 from www.xfree86.org make World, make install and all was solved. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
