I tried, in tcsh:
% setenv |grep FR
XTERM_LOCALE=fr_FR.ISO8859-1
LC_CTYPE=fr_FR.ISO8859-1
but the accented French characters are corrupted, e.g. in
/usr/ports/french/aster/pkg-descr.
I built xterm with
% make -C /usr/ports/x11/xterm showconfig
=== The following configuration options
* Anton Shterenlikht me...@bris.ac.uk [2013-07-17 13:14 +0100]:
I tried, in tcsh:
% setenv |grep FR
XTERM_LOCALE=fr_FR.ISO8859-1
LC_CTYPE=fr_FR.ISO8859-1
but the accented French characters are corrupted, e.g. in
/usr/ports/french/aster/pkg-descr.
I built xterm with
% make -C
. in
/usr/ports/french/aster/pkg-descr.
I built xterm with
% make -C /usr/ports/x11/xterm showconfig
=== The following configuration options are available for xterm-296:
256COLOR=on: Enable 256-color support
DABBREV=off: Enable support for dabbrev-expand
DECTERM=off
Date: Wed, 17 Jul 2013 22:57:34 +0200
From: Polytropon free...@edvax.de
To: Elimar Riesebieter riese...@lxtec.de
Subject: Re: LC_CTYPE=fr_FR.ISO8859-1 with xterm - still French accented
characters are corrupted
On Wed, 17 Jul 2013 15:38:53 +0200, Elimar Riesebieter wrote:
* Anton Shterenlikht
are the same in both cases.
I run Xorg on both systems along with open-motif and xterms:
xorg-7.5.2
open-motif-2.3.4
xterm-292
The /var/db/ports/xterm/options files on both systems are identical.
# This file is auto-generated by 'make config'.
# Options for xterm-292
_OPTIONS_READ=xterm-292
23.11.2012 06:22, Gary Aitken:
Do you have a nvidia card ?
If yes right click on the youtube image and disable hardware acceleration,
it will probably solve it (solved for me)
I'm seeing this too. nvidia-driver is installed. I'm using E17 without opengl.
While this should work for flash
doesn't), I now see that when I put an xterm
window over a particular portion of the display, the black areas on the
xterm are transparent, and are showing a portion of a youtube page
which is no longer playing but which is still open on either a visible
or a non-visible (i.e. not the current) tab
solve it (solved for me)
2012/11/21 Gary Aitken free...@dreamchaser.org
After doing a number of port upgrades to try to get firefox 16 to play
youtube audio again (still doesn't), I now see that when I put an xterm
window over a particular portion of the display, the black areas on the
xterm
on the youtube image and disable hardware acceleration,
it will probably solve it (solved for me)
2012/11/21 Gary Aitken free...@dreamchaser.org
After doing a number of port upgrades to try to get firefox 16 to play
youtube audio again (still doesn't), I now see that when I put an xterm
window
On 11/22/12 08:10, Volodymyr Kostyrko wrote:
22.11.2012 16:33, David Demelier:
Do you have a nvidia card ?
If yes right click on the youtube image and disable hardware acceleration,
it will probably solve it (solved for me)
I'm seeing this too. nvidia-driver is installed. I'm using E17
After doing a number of port upgrades to try to get firefox 16 to play
youtube audio again (still doesn't), I now see that when I put an xterm
window over a particular portion of the display, the black areas on the
xterm are transparent, and are showing a portion of a youtube page
which
in a xterm window, some parts of them are coming
out a bit garbled.
I'm sure that there must be some recommended option or options for
xterm that will cause man pages to display properly. If someone would
tell me what those options are, I would appreciate it. Thanks
on Sat 6.Oct'12 at 2:25:04 -0700 ]
When I view man pages in a xterm window, some parts of them are coming
out a bit garbled.
I'm sure that there must be some recommended option or options for
xterm that will cause man pages to display properly. If someone
When I view man pages in a xterm window, some parts of them are coming
out a bit garbled.
I'm sure that there must be some recommended option or options for
xterm that will cause man pages to display properly. If someone would
tell me what those options are, I would appreciate it. Thanks
[ Ronald F. Guilmette wrote on Sat 6.Oct'12 at 2:25:04 -0700 ]
When I view man pages in a xterm window, some parts of them are coming
out a bit garbled.
I'm sure that there must be some recommended option or options for
xterm that will cause man pages to display properly. If someone
On Sat, Oct 06, 2012 at 07:31:07AM -0400, Thomas Dickey wrote:
On Sat, Oct 06, 2012 at 10:45:52AM +0100, Jamie Paul Griffin wrote:
[ Ronald F. Guilmette wrote on Sat 6.Oct'12 at 2:25:04 -0700 ]
When I view man pages in a xterm window, some parts of them are coming
out a bit
On Sat, Oct 06, 2012 at 10:45:52AM +0100, Jamie Paul Griffin wrote:
[ Ronald F. Guilmette wrote on Sat 6.Oct'12 at 2:25:04 -0700 ]
When I view man pages in a xterm window, some parts of them are coming
out a bit garbled.
I'm sure that there must be some recommended option
for enabling/disabling.
I tried to set environment variable TERM = xterm to TERM = cons25
since I thought this could be a problem with the terminal. But it
wans't. Either the outdated X on FBSD causes problems or there is
another issue. I desperately need some help ...
Regards and thanks in advance
is that I can not use DEL key to delete
characters or even use the ALT key to enforce actions like ALT-e or
ALT-d for enabling/disabling.
I tried to set environment variable TERM = xterm to TERM = cons25
since I thought this could be a problem with the terminal. But it
wans't. Either the outdated X
kiddy-cloaking scripting environment,
called YAST/YAST2.
[...]
Of course, it is either setenv TERM xterm in csh or TERM=xterm in
bourne-alike shells.
Hi Oliver,
DEL and BS (Backspace) are one of those things where terminals have
failed to standardize. Remember there are *many* layers
On Mon, Mar 12, 2012 at 11:43:17AM -0400, Alejandro Imass wrote:
Take a look at this article and you will probably fix the problem, and
it's probably not even on the FBSD side:
www.ibb.net/~anne/keyboard.html
not really (that page gives a lot of poor advice, particularly with regard
to xterm
On Mon, Mar 12, 2012 at 03:30:58PM +0100, O. Hartmann wrote:
And you are using xterm (not rxvt)?
No, pure and plain and conservative xterm as it comes with the port and
no extravagant terminal thingy.
Linux generally uses DEL (127) and (almost) everyone else uses BS (8).
Adding
Since the X11-update from libraries and applications 1.4 - 1.5 the
xterminal keyboard beeping, disabled by 'xset -b' or 'xset b off'
doesn't work. In xterm, I get beeping although I disabled beeping via
the above mentioned xset command.
Regards,
Oliver
On 10-05-2010 19:34, O. Hartmann wrote:
Since the X11-update from libraries and applications 1.4 - 1.5 the
xterminal keyboard beeping, disabled by 'xset -b' or 'xset b off'
doesn't work. In xterm, I get beeping although I disabled beeping via
the above mentioned xset command.
Me too.
I
I have code window showing in gdb (Ctrl-X a), and all is fine.
After I put gdb into background (Ctrl-Z) and back (fg) Ctrl-X stops working.
Pressing Ctrl-X just causes ^X to appear.
I think some terminal settings aren't right after coming back from
background. How to fix this?
I use kde4 and
Christian Weisgerber na...@mips.inka.de wrote:
Short:
--
Why do compose key sequences fail to work in a UTF-8 xterm?
And the short answer is: They work--if you know the right sequences.
The compose key handling presumably comes out of some X11
library; xterm is just the recipient
On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote:
Short:
--
Why do compose key sequences fail to work in a UTF-8 xterm?
The port x11/rxvt-unicode is lighter on resources then xterm, and works fine
with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set)
Roland
On Sun, Mar 14, 2010 at 12:45:24PM +0100, Roland Smith wrote:
On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote:
Short:
--
Why do compose key sequences fail to work in a UTF-8 xterm?
The port x11/rxvt-unicode is lighter on resources then xterm, and works fine
Roland Smith:
Why do compose key sequences fail to work in a UTF-8 xterm?
The port x11/rxvt-unicode is lighter on resources then xterm, and works fine
with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set)
You didn't bother to read and understand my question, did you?
urxvt shows
On Sun, Mar 14, 2010 at 01:43:27PM +0100, Christian Weisgerber wrote:
Roland Smith:
Why do compose key sequences fail to work in a UTF-8 xterm?
The port x11/rxvt-unicode is lighter on resources then xterm, and works fine
with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set
Nothing of susbtance here ...
in message 20100314114524.gb25...@slackbox.erewhon.net,
wrote Roland Smith thusly...
On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote:
Short:
--
Why do compose key sequences fail to work in a UTF-8 xterm?
The port x11/rxvt-unicode
Short:
--
Why do compose key sequences fail to work in a UTF-8 xterm?
Long:
-
I have configured a compose key (aka Multi_key) here:
$ setxkbmap -layout us -option compose:ralt
When I start an xterm with an ISO8859-1 locale
$ LC_CTYPE=en_US.ISO8859-1 xterm
I can use the compose key
If your video card and monitor combination supports underlining this
might be worth pursuing. Many VGA-compatible cards do not, and text-mode
hmm. my knowledge of VGA programming is from 386 times, but i remember it
to be a standard - underline or ability to display another 256 characters
-
I'd like to ask the following question: Can the syscons driver
be configured in a way that certain screen attributes are
displayed in the same way? Read: It is possible to use the
underline attribute in text mode?
For example, when I call man man in an xterm, the effect
is this, black on white
On Mon, 1 Jun 2009, Polytropon wrote:
I'd like to ask the following question: Can the syscons driver
be configured in a way that certain screen attributes are
displayed in the same way? Read: It is possible to use the
underline attribute in text mode?
If your video card and monitor
Hi,
I want to use ssh to connect to a remote machine, launch an xterm with
the IP address of my X server display and exit ssh (there is no need
to have ssh idled once xterm has started).
I beleive that can be done in a single command, but I am clueless
about the syntax.
I am pretty much aware
Occasionally, one wants to do this. Unfortunately this is one of
those topics with too many generic search terms that gives 2.99x10e8
hits. Clearly, I'm suffering from information overload both in my
console sessions and my google searches ;)
Steve
google searches ;)
Ctl-L does it for me in xterm. Might work in the console too.
Steve
Anybody know how to clear the buffer in screen?
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
___
freebsd-questions@freebsd.org
Ctl-L does it for me in xterm. Might work in the console too.
Just clears the screen, not the scrollback buffer for me. Must be
some secret setting somewhere...
Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman
On Thu, Jan 22, 2009 at 02:50:09PM -0700, Steve Franks wrote:
Ctl-L does it for me in xterm. Might work in the console too.
Just clears the screen, not the scrollback buffer for me. Must be
some secret setting somewhere...
Sorry Steve, I forgot to mention that I've got:
XTerm*VT100
On Thu, Jan 22, 2009 at 01:49:13PM -0700, Steve Franks wrote:
Occasionally, one wants to do this. Unfortunately this is one of
those topics with too many generic search terms that gives 2.99x10e8
hits. Clearly, I'm suffering from information overload both in my
console sessions and my
, I'm suffering from information overload both in my
console sessions and my google searches ;)
Ctl-L does it for me in xterm. Might work in the console too.
Works there, but you can still press the Scroll Lock key and then
use the cursor / page moving keys to check what's up there.
If you
of xterms and a clock, if you know the
one...
and then type 'startkde' in one of those.
kde starts, but what i'm interested in, is that the xterm i started kde from
keeps displaying messages - which on a few occasions seemed very clean, on
others i noticed warnings - like bad window, etc.
now i'm
x11
with 'startx' without any .xinitrc file whatsoever - so i could go to the
basic x that starts with a couple of xterms and a clock, if you know the
one...
and then type 'startkde' in one of those.
kde starts, but what i'm interested in, is that the xterm i started kde from
keeps
On Mon, Feb 04, 2008 at 12:41:13AM +, Chris Whitehouse wrote:
it's a stupid little question really but I have an xterm filled with a
log file (telnetted into another machine) which is scrolled off the
screen. How do I select all the text in one go? I only seem to be able
to select
Robert Huff wrote:
Chris Whitehouse writes:
it's a stupid little question really but I have an xterm filled
with a log file (telnetted into another machine) which is
scrolled off the screen.
If you can telnet, can you ftp?
Robert Huff
it's a stupid little question really but I have an xterm filled with a
log file (telnetted into another machine) which is scrolled off the
screen. How do I select all the text in one go? I only seem to be able
to select the visible screenful, copy, paste into text file, scroll up,
select
Chris Whitehouse writes:
it's a stupid little question really but I have an xterm filled
with a log file (telnetted into another machine) which is
scrolled off the screen.
If you can telnet, can you ftp?
Robert Huff
Chris Whitehouse [EMAIL PROTECTED] writes:
it's a stupid little question really but I have an xterm filled with a
log file (telnetted into another machine) which is scrolled off the
screen. How do I select all the text in one go? I only seem to be able
to select the visible screenful, copy
swell k writes:
swell Chris Whitehouse [EMAIL PROTECTED] writes:
it's a stupid little question really but I have an xterm filled with a
log file (telnetted into another machine) which is scrolled off the
screen. How do I select all the text in one go? I only seem to be able
like this.
A few stabs in the dark:
What happened if you used no xorg.conf at all? Did you get the
same xterm problem?
Do you have a locale set?
Thanks for the response.
1. If I try to running with no xorg.conf, it just hangs. I think
the equipment is too old
Lowell Gilbert wrote:
Hmm. I've never heard of any symptoms quite like this.
A few stabs in the dark:
What happened if you used no xorg.conf at all? Did you get the same
xterm problem?
Do you have a locale set?
Thanks for the response.
1. If I try to running with no xorg.conf
Lowell Gilbert wrote:
Hmm. I've never heard of any symptoms quite like this.
A few stabs in the dark:
What happened if you used no xorg.conf at all? Did you get the same
xterm problem?
Do you have a locale set?
Thanks for the response.
1. If I try to running with no xorg.conf
On Sun, 15 Jul 2007 19:15:03 -0500
Michael Gass [EMAIL PROTECTED] wrote:
Lowell Gilbert wrote:
Hmm. I've never heard of any symptoms quite like this.
A few stabs in the dark:
What happened if you used no xorg.conf at all? Did you get the same
xterm problem?
Do you have
at all? Did you get the same
xterm problem?
Do you have a locale set?
Thanks for the response.
1. If I try to running with no xorg.conf, it just hangs. I think the
equipment is too old for the defaults.
2. My locale is set to C
3. If I set the DefaultDepth to 1 in Screen
Hmm. I've never heard of any symptoms quite like this.
A few stabs in the dark:
What happened if you used no xorg.conf at all? Did you get the same
xterm problem?
Do you have a locale set?
___
freebsd-questions@freebsd.org mailing list
http
Just installed Xorg 7.2 on an old 486DX cpu machine (Compaq ProLinea)
running FreeBSD (Just to do it!). Only an old vga card.
I can run the server and startx brings up twm, but I have garbled text
in the xterm; that is, the wrong letters and symbols come up when xterm
opens and when I type
David Coder [EMAIL PROTECTED] writes:
i'm used to being able to use ctrl-right mouse key to enlarge my xterms
but since (i think) an upgrade to the 7.2 xorg libraries that combination
gives me a choice between fonts font modalities i can't figure out how to
get the old functionality back.
i'm used to being able to use ctrl-right mouse key to enlarge my xterms
but since (i think) an upgrade to the 7.2 xorg libraries that combination
gives me a choice between fonts font modalities i can't figure out how to
get the old functionality back. clues?
thx.
david
I presently access FBSD via an xterm window from within Windows using
X-Win32. I would like to be able to run a window manager or file manager,
but this exits with an error because there is no mouse attached to the
FBSD box.
Here is the thing - I -can- run xv (a FBSD image viewer from the ports
Pieter de Goeje wrote:
On Saturday 02 June 2007, Jeremy Gransden wrote:
Hello,
I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my
On Tue, 5 Jun 2007, Tek Bahadur Limbu wrote:
Pieter de Goeje wrote:
On Saturday 02 June 2007, Jeremy Gransden wrote:
Hello,
I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start
Hello,
I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop, how
can I then connect to it from my laptop and see the output of that
On Sat, Jun 02, 2007 at 07:23:45AM -0400, Jeremy Gransden wrote:
Hello,
I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop,
, or
attach/detach at will. Quite good if, for example you're running a
process (within a screen session, of course!) in an xterm, and you
want to restart X. Simply detach the screen session, restart X, then
reattach screen to your xterm.
--
Regards,
Paul Fraser
http://furyc0de.net
On Saturday 02 June 2007, Jeremy Gransden wrote:
Hello,
I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop, how
can I then
On Sat, Jun 02, 2007 at 01:39:08PM +0200, Roland Smith wrote:
If you want to keep tabs on an already running process, you should start
the process in such a way that it redirects the standard output and
standard error streams to a file. How that's done depends on the shell
you're using. You
, then you can share the session from any number of clients, or
attach/detach at will. Quite good if, for example you're running a
process (within a screen session, of course!) in an xterm, and you
want to restart X. Simply detach the screen session, restart X, then
reattach screen to your xterm
[EMAIL PROTECTED] (Bob Middaugh) writes:
Hi everyone,
I installed 6.2 and chose X-Developer for the distribution. After the
install, but still in sysinstall, chose gnome from the packages. When gnome
finished installing, I rebooted. I did startx as root and got the xterm, but
when I
Hi everyone,
I installed 6.2 and chose X-Developer for the distribution. After the install,
but still in sysinstall, chose gnome from the packages. When gnome finished
installing, I rebooted. I did startx as root and got the xterm, but when I
typed gdm from the prompt, nothing happened
On 4/14/06, Rostislav Krasny [EMAIL PROTECTED] wrote:
About a month ago UTF-8 locale stopped working in my xterm.
I experience the same problem after the xterm port had been updated
from 206 to 210 version. As a workaround you can either: downgrade to
xterm-206 or use uxterm. I'm suspecting
About a month ago UTF-8 locale stopped working in my xterm.
I fail to find comprehensive documentation on fonts in X11
and therefore I fail to fully understand and trace the problem.
I'll be most grateful if somebody leads me to a source of
fine docs, but I'm really full of doubt after much
About a month ago UTF-8 locale stopped working in my xterm.
I experience the same problem after the xterm port had been updated
from 206 to 210 version. As a workaround you can either: downgrade to
xterm-206 or use uxterm. I'm suspecting following change of xterm-209:
amend change for loading
Hello!
I upgraded X-server to xorg-6.9.0 a month ago. Since then, xfontsel
would not start and xterm crashes when I try to bring up any of its
three menus by pressing any of the mouse buttons while holding Ctrl.
The messages are always the same:
Warning: Unable to load any usable
, Kent Stewart [EMAIL PROTECTED] wrote:
On Saturday 18 February 2006 12:08, Xn Nooby wrote:
its depressing when a fresh install fails
i followed my normal fail-proof slow method of updating a fresh
install, and it fails to update xterm, some of the messages are:
== xterm-206_1
its depressing when a fresh install fails
i followed my normal fail-proof slow method of updating a fresh install, and
it fails to update xterm, some of the messages are:
== xterm-206_1 conflicts with installed packages:
xorg-clients-6.8.2
*** Error code 1
** Listing the failed
On Saturday 18 February 2006 12:08, Xn Nooby wrote:
its depressing when a fresh install fails
i followed my normal fail-proof slow method of updating a fresh
install, and it fails to update xterm, some of the messages are:
== xterm-206_1 conflicts with installed packages:
xorg-clients
decided to play with the value of $TERM.
By default, when I ssh FreeBSD via PuTTY or Apple Terminal, I have the
TERM variable set to xterm or xterm-color. When I tried to
manually change $TERM on FreeBSD and run ee, using setenv TERM vt102
ee test.txt, then Backspace key in ee(1) did behave
, I've noticed that it does not do that when I
login via console.
So I decided to play with the value of $TERM.
By default, when I ssh FreeBSD via PuTTY or Apple Terminal, I have the
TERM variable set to xterm or xterm-color. When I tried to
manually change $TERM on FreeBSD and run ee
Constantine A. Murenin wrote:
They map it perfectly fine as 127, it's only FreeBSD's ee(1) that has
this problem, tcsh and others work fine.
ee does not do this on the console on my 5.4 machine, nor does it
do this in an XTerm over an ssh connection to my 4.11 machine,
therefore I would
ssh FreeBSD via PuTTY or Apple Terminal, I have the
TERM variable set to xterm or xterm-color. When I tried to
manually change $TERM on FreeBSD and run ee, using setenv TERM vt102
ee test.txt, then Backspace key in ee(1) did behave as expected.
Please, notice that Backspace does behave as expected
worked you can say portupgrade -w x11/xorg-clients
which should install what you have just rebuilt. The patch will survive
csvup and would need to be deleted if this issue is ever fixed.
Then portupgrade x11/xterm should work fine.
--Alex
Thanks alot, but it worked to deinstall nvidia
Hello.
While updating my installed ports via portsnap/portupgrade I receive
this error since yesterday's portsnap fetch while building xterm-206:
--- Uninstalling the old version
--- Deinstalling 'xterm-206'
pkg_delete: package 'xterm-206' is required by these other packages
and may
O. Hartmann wrote:
=== 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
Stop in /usr/ports/x11/xterm.
*** Error code 1
Stop in /usr/ports/x11/xterm
Kevin Kinsey wrote:
O. Hartmann wrote:
=== 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
Stop in /usr/ports/x11/xterm.
*** Error code 1
Stop in /usr
=== 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
Stop in /usr/ports/x11/xterm.
*** Error code 1
Stop in /usr/ports/x11/xterm.
** Command failed
After running cvsup and portupgrade, I'm having some problems with xterm
and some other programs.
Portupgrade failed because of the following:
=== xterm-206_1 conflicts with installed package(s):
xorg-clients-6.8.2
They install files into the same place.
Please remove them
Jeppe Larsen wrote:
After running cvsup and portupgrade, I'm having some problems with xterm
and some other programs.
Portupgrade failed because of the following:
=== xterm-206_1 conflicts with installed package(s):
xorg-clients-6.8.2
They install files into the same place
On Mon, Nov 14, 2005 at 05:22:08PM +, Alex Zbyslaw wrote:
Jeppe Larsen wrote:
After running cvsup and portupgrade, I'm having some problems with xterm
and some other programs.
Portupgrade failed because of the following:
=== xterm-206_1 conflicts with installed package(s
Check /usr/ports/UPDATING. There should be a fairly recent
entry discussing how to deal with this. Actually it is the first
listing in /usr/ports/UPDATING
20051113:
AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients
AUTHOR: [EMAIL PROTECTED]
Xterm no longer installs
On Mon, 14 Nov 2005 17:22:08 +, Alex Zbyslaw wrote:
Don't delete any of those dependencies! If you do then you will
probably have to re-install those packages to get the dependencies back.
I believe upgrading xorg-clients and then xterm should work, if only
that damn xorg-clients port
Mike Hernandez wrote:
On Mon, Nov 14, 2005 at 05:22:08PM +, Alex Zbyslaw wrote:
Jeppe Larsen wrote:
After running cvsup and portupgrade, I'm having some problems with xterm
and some other programs.
Portupgrade failed because of the following:
=== xterm-206_1 conflicts
On Mon, Nov 14, 2005 at 05:59:40PM +, Alex Zbyslaw wrote:
I don't think so. Keep track of which ports you deleted the
dependencies from, then when you have the whole xorg-clients/xterm mess
sorted out, just force a re-install of those packages and the right
dependencies will come back
Jeppe Larsen wrote:
On Mon, 14 Nov 2005 17:22:08 +, Alex Zbyslaw wrote:
I believe upgrading xorg-clients and then xterm should work, if only
that damn xorg-clients port would compile! I found this link late last
night which might help, but haven't tried it myself yet.
http
Eric Ekong wrote:
Check /usr/ports/UPDATING. There should be a fairly recent
entry discussing how to deal with this. Actually it is the first
listing in /usr/ports/UPDATING
20051113:
AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients
AUTHOR: [EMAIL PROTECTED]
Xterm
On 2005-11-14 13:07, Mike Hernandez [EMAIL PROTECTED] wrote:
On Mon, Nov 14, 2005 at 05:59:40PM +, Alex Zbyslaw wrote:
I don't think so. Keep track of which ports you deleted the
dependencies from, then when you have the whole
xorg-clients/xterm mess sorted out, just force a re-install
On Monday, November 14, 2005 12:42:14 PM, Mike Hernandez [EMAIL PROTECTED]
Subject: Re: xterm conflicts with xorg-clients
Wrote these words of wisdom:
On Mon, Nov 14, 2005 at 05:22:08PM +, Alex Zbyslaw wrote:
Jeppe Larsen wrote:
After running cvsup and portupgrade, I'm having some
On Monday 14 November 2005 09:02, Jeppe Larsen wrote:
After running cvsup and portupgrade, I'm having some problems with xterm
and some other programs.
Portupgrade failed because of the following:
=== xterm-206_1 conflicts with installed package(s):
xorg-clients-6.8.2
On Mon, Nov 14, 2005 at 10:24:45AM -0800, Giorgos Keramidas wrote:
New releases of xterm are made far more often than full X11
releases, so it makes more sense I guess. Every time a new
version of xterm is out, you don't really need to download
rebuild monster-tarballs with all the X11
and then xterm should work, if
only that damn xorg-clients port would compile! I found this link
late last night which might help, but haven't tried it myself yet.
http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040
.html
If you don't want to do all that then you'll have
1 - 100 of 236 matches
Mail list logo
