On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote:
> I do understand that a bit. Other than that plain termcap was so
> small and i would assume essentially unchanged for decades, that
> i do not. Termcap entries, yes. I could imagine vt220, xterm,
> screen-256color, and take one
On Tue, Oct 31, 2023 at 10:59:48PM +, Jamie Landeg-Jones wrote:
> Jamie Landeg-Jones wrote:
>
> > switch to tcsh, and reinitialise terminal information:
> >
> > % setenv TERM dumb
> > % setenv TERM xterm
>
> % setenv TERM xterm-256color
>
> Apologies, it seems this doesn't affect plain
On Fri, Apr 07, 2023 at 09:51:30AM -0500, Dan Mack wrote:
>
> I recently logged into one of my FreeBSD systems from an alacritty terminal.
> FreeBSD didn't have a termcap entry for alacritty so I generated one with
> tic and all was well. However, I noticed the following issues with the
> TERM*
On Fri, Oct 22, 2021 at 04:11:56PM +, Baptiste Daroussin wrote:
>
> 22 oct. 2021 18:06:56 John Baldwin :
>
> > On 10/22/21 1:08 AM, Mark Millard via freebsd-current wrote:
> >> main [soi: 14] commit a96ef450 (2021-02-26 09:16:49 +)
> >> changed DIALOG_STATE, DIALOG_VARS, and
On Sat, Apr 03, 2021 at 02:36:29PM -0400, Thomas Dickey wrote:
...
attaching trace :-)
--
Thomas E. Dickey
https://invisible-island.net
ftp://ftp.invisible-island.net
TRACING NCURSES version 6.2.20210403 (tracelevel=0x)
called {setupterm("screen",2,0x7fffe2b0)
your ter
On Wed, Mar 31, 2021 at 07:54:09PM -0400, Thomas Dickey wrote:
> On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote:
> > On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
> > >
> > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
>
On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote:
> On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
> >
> > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
> > >
> > >>
> > >> Knowing that would help me see w
On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
>
> > On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
> >
> >>
> >> Knowing that would help me see whether the problem is faulty initialization
> >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
> >> the
ount > 0; nullcount--)
>104 my_outch(NCURSES_SP_ARGx PC);
>105 if (my_outch == NCURSES_SP_NAME(_nc_outch))
>106 NCURSES_SP_NAME(_nc_flush) (NCURSES_SP_ARG);
>
> Application is using term_styled_ostream_create() that does not initialize
> default
On Mon, Mar 29, 2021 at 12:12:55PM -0700, Henric Jungheim wrote:
>
> I ran into a bit of an odd problem when building the
> sysutils/grub2-bhyve port on 13.0-RC3 (on x64). The bison command
> dumps core when the output is going to a console. Redirecting the
> build output to a file avoids the
On Tue, Feb 25, 2020 at 10:27:37AM +0100, Baptiste Daroussin wrote:
> On Tue, Feb 25, 2020 at 04:19:56AM -0500, Thomas Dickey wrote:
> > On Mon, Feb 24, 2020 at 08:28:03PM -0500, Thomas Dickey wrote:
> > > On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote:
> >
On Mon, Feb 24, 2020 at 08:28:03PM -0500, Thomas Dickey wrote:
> On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote:
> > On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote:
> > > On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote:
> >
On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote:
> On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote:
> > On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote:
> > > From: "O. Hartmann"
> > > Subject: r358062(ncurses
On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote:
> On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote:
> > From: "O. Hartmann"
> > Subject: r358062(ncurses) breaks installed ports, howto check?
> > Date: Mon, 24 Feb 2020 20:19:59 +0100
On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote:
> From: "O. Hartmann"
> Subject: r358062(ncurses) breaks installed ports, howto check?
> Date: Mon, 24 Feb 2020 20:19:59 +0100
>
> > After r358062, many installed ports do not work anymore on several running
> > systems (CURRENT).
On Mon, Jun 06, 2016 at 10:12:14PM -0700, Tim Rice wrote:
>
> Would someone please commit the attached termcap patch for Altos V
> terminals.
> Granted I may be the only person still using one but it'll save
> continual patching.
> Thanks for your consideration.
>
> --
> Tim Rice
>
On Tue, Dec 15, 2015 at 04:01:41PM +0100, Carsten Kunze wrote:
> Hello,
>
> current groff doesn't build on FreeBSD. I had noticed the same issue some
> months ago on NetBSD and cross checked on FreeBSD and it had worked on
> FreeBSD. There must have somethig changed since then. How to
On Wed, Oct 05, 2011 at 04:17:16PM +, Christian Weisgerber wrote:
Anton Shterenlikht me...@bristol.ac.uk wrote:
BUZI groff -ms -Tascii try.1 | more
ESC[1mSome titleESC[0m
How can I get a plain text rendering
from a troff document with ms macros?
On Wed, Oct 05, 2011 at 09:01:32PM +0100, Anton Shterenlikht wrote:
The reason for writing to current@ is
that I've one box still on r216048,
where -c flag is not required.
Has there been a recent change to groff,
affecting this behaviour?
As I recall it, the behavior is also configurable
On Tue, Aug 09, 2011 at 08:31:13AM -0600, Warren Block wrote:
On Mon, 8 Aug 2011, Kevin Oberman wrote:
I think this behavior (already in several Linux distros) is really far more
intuitive that the old FreeBSD version, but it is a bit disconcerting at
first. It really does not take much to
On Sat, Jun 04, 2011 at 05:54:49AM +0400, Andrey Chernov wrote:
On Fri, Jun 03, 2011 at 02:48:59PM +, Ruslan Ermilov wrote:
On a freshly installed -CURRENT, to view a colorized manpage in color
and in full terminal width, try this:
env MANCOLOR=yes MANWIDTH=tty man grotty
On Mon, Apr 25, 2011 at 09:52:24AM +0200, Gary Jennejohn wrote:
On Sun, 24 Apr 2011 20:23:14 -0400
Thomas Dickey dic...@radix.net wrote:
On Mon, Apr 25, 2011 at 08:37:05AM +0900, Randy Bush wrote:
no help from the following:
*** termcap~Fri Mar 18 14:34:01 2011
--- termcap
On Mon, Apr 25, 2011 at 01:12:54PM +0200, Gary Jennejohn wrote:
Mine sets it to rxvt.
I tried setting TERM to rxvt in xterm, but of course it didn't work.
I overlooked asking whether Randy had regen'd the termcap.db file
which is presumably used for the updated termcap. A truss/ktrace
would
On Tue, Apr 26, 2011 at 01:10:58AM +0300, Kostik Belousov wrote:
On Mon, Apr 25, 2011 at 05:38:26PM -0400, Thomas Dickey wrote:
On Mon, Apr 25, 2011 at 01:12:54PM +0200, Gary Jennejohn wrote:
Mine sets it to rxvt.
I tried setting TERM to rxvt in xterm, but of course it didn't work
On Tue, Apr 26, 2011 at 07:41:38AM +0900, Randy Bush wrote:
I overlooked asking whether Randy had regen'd the termcap.db file
which is presumably used for the updated termcap.
i did
I sort of assumed you did, but am still puzzled where the problem lies.
--
Thomas E. Dickey
On Sun, Apr 24, 2011 at 02:57:11PM +0900, Randy Bush wrote:
i know i a perverted, but i really prefer not to have ca_mode. i.e.
prior to 9, i had this little patch
*** termcap.FCS Tue Jun 17 15:10:46 2003
--- termcap Tue Jun 17 15:14:15 2003
***
*** 299,305
On Sun, Apr 24, 2011 at 07:30:12PM +0900, Randy Bush wrote:
With xterm?
yep
What does the included termcap for xterm-xfree86 look like?
Just to refresh my memory, I'm looking at the code, and see
that titeInhibit applies to each of the controls that would switch
between normal/alternate
On Sun, Apr 24, 2011 at 10:23:43PM +0900, Randy Bush wrote:
What does the included termcap for xterm-xfree86 look like?
xterm-new|modern xterm:\
...
looks ok - no hidden ti or te capabilities lurking in that.
odd - even if you were using an application that uses the terminfo
entry
On Sun, Apr 24, 2011 at 06:26:34PM -0400, Thomas Dickey wrote:
On Mon, Apr 25, 2011 at 01:04:56AM +0400, Pan Tsu wrote:
Randy Bush ra...@psg.com writes:
i know i a perverted, but i really prefer not to have ca_mode. i.e.
Not to? But the patch makes the opposite effect.
hmm - I've
On Mon, Apr 25, 2011 at 01:04:56AM +0400, Pan Tsu wrote:
Randy Bush ra...@psg.com writes:
i know i a perverted, but i really prefer not to have ca_mode. i.e.
Not to? But the patch makes the opposite effect.
hmm - I've seen this sort of question often enough that I read it offhand
as did
On Mon, Apr 25, 2011 at 08:37:05AM +0900, Randy Bush wrote:
no help from the following:
*** termcap~Fri Mar 18 14:34:01 2011
--- termcap Sun Apr 24 23:33:52 2011
***
*** 3131,3136
--- 3131,3137
#
# Customization begins here.
xterm-xfree86|xterm
On Fri, Mar 25, 2011 at 11:54:35AM -0500, Eitan Adler wrote:
On Fri, Mar 25, 2011 at 11:35 AM, Andriy Gapon a...@freebsd.org wrote:
on 25/03/2011 17:35 Pietro Cerutti said the following:
No need to look for strange scenarios, I'm surely going to sudo rm -f the
file
more sooner than
On Wed, Feb 09, 2011 at 10:28:53AM -0500, David Boyd wrote:
Having some time to test 9.0-CURRENT with the new dialog command has
uncovered only one major omission (for us): prgbox/dialog_prgbox.
This is used in most (if not all) of our installation/management scripts.
Was prgbox omitted
On Tue, Aug 03, 2010 at 11:22:36AM -0700, Julian Elischer wrote:
On 8/3/10 2:34 AM, pluknet wrote:
Hi.
I looked into sys/kern/* files to fix a bunch of common w/s style issues
(221):
- leading space before label;
- leading space(s) beforetab;
- space(s) instead oftab(s);
- space(s) in
On Tue, Jul 22, 2003 at 02:56:37PM -0500, Jacques A. Vidrine wrote:
On Tue, Jul 22, 2003 at 02:26:08PM +0200, Simon Barner wrote:
--- plugins/check_by_ssh.c.orig Mon Apr 23 09:43:11 2001
+++ plugins/check_by_ssh.c Tue Jul 22 05:05:52 2003
@@ -191,7 +191,7 @@
if (commands1)
On Mon, Jul 07, 2003 at 10:22:02AM +0200, Juan Rodriguez Hervella wrote:
(still waiting for FreeBSD to complete a sysinstall program that doesn't
look as if it was an assignment for high-school interns).
What's the matter with sysinstall ?
I very much like sysinstall as it is now. :)
to
On Mon, Jul 07, 2003 at 02:23:25PM +0200, Marcin Dalecki wrote:
You know that file system name lookup is one of the most
expensive system calls under UNIX?
stating the obvious is a clumsy rhetorical ploy (asking for agreement without
making a point).
--
Thomas E. Dickey [EMAIL PROTECTED]
On Mon, Jul 07, 2003 at 03:35:21PM +0200, Marcin Dalecki wrote:
Thomas Dickey wrote:
On Mon, Jul 07, 2003 at 02:23:25PM +0200, Marcin Dalecki wrote:
You know that file system name lookup is one of the most
expensive system calls under UNIX?
stating the obvious is a clumsy rhetorical
On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote:
Myron J. Mayfield wrote:
I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar
file only unpacked part of it. I then copied the files from my Redhat 9
machine. I linked up all the linux libraries needed and
I'm setting up a new machine, and none of the current *BSD's install on it.
Linux works. The *BSD's choke during the device identification. Perhaps
someone on this list knows why. Attaching a copy of dmesg output from one
of the Linux's I installed. The *BSD's appear to be missing an interrupt
On Wed, Jun 25, 2003 at 11:37:30PM +0900, Hideyuki KURASHINA wrote:
Hi,
On Wed, 25 Jun 2003 09:49:50 -0400, Thomas Dickey [EMAIL PROTECTED] said:
I'm setting up a new machine, and none of the current *BSD's install on it.
Linux works. The *BSD's choke during the device identification
On Wed, Jun 25, 2003 at 04:56:56PM +0200, Soeren Schmidt wrote:
It seems Hideyuki KURASHINA wrote:
From your attached dmesg,
PCI: Using IRQ router SIS [1039/0008] at 00:02.0
[...]
SIS5513: IDE controller on PCI bus 00 dev 15
PCI: Found IRQ 5 for device 00:02.5
SIS5513: chipset
42 matches
Mail list logo
