[Touch-packages] [Bug 1999171] Re: tparm dynamic variables broken

https://invisible-island.net/ncurses/man/terminfo.5.html#h3-Parameterized-Strings https://invisible-island.net/personal/bug-reports.html#low_support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu.

Re: [Lynx-dev] Porting the configure script to C99

On Fri, Dec 02, 2022 at 11:16:32PM +0100, Florian Weimer wrote: > * Thomas Dickey: > > >> diff --git a/configure b/configure > >> index 97f6d1d5646d05c5..6db52b514b3b9a3c 100755 > >> --- a/configure > >> +++ b/configure > >> @@ -31

Re: [Lynx-dev] Porting the configure script to C99

On Fri, Dec 02, 2022 at 04:04:32PM +0100, Florian Weimer wrote: > We're trying to build Fedora with a strict(er) C99 compiler: > > > > > Testing I dentified a couple of

Re: CI commit checks (was: [ANNOUNCE] libXft 2.3.7)

On Wed, Nov 30, 2022 at 04:57:04PM -0800, Alan Coopersmith wrote: > On 11/16/22 01:08, Thomas Dickey wrote: > > On Tue, Nov 15, 2022 at 03:27:38PM -0500, Thomas E. Dickey wrote: > > > Thomas E. Dickey (4): > > >libxft issue #15 > > >fix compil

Re: CI commit checks (was: [ANNOUNCE] libXft 2.3.7)

On Wed, Nov 30, 2022 at 04:57:04PM -0800, Alan Coopersmith wrote: > On 11/16/22 01:08, Thomas Dickey wrote: > > On Tue, Nov 15, 2022 at 03:27:38PM -0500, Thomas E. Dickey wrote: > > > Thomas E. Dickey (4): > > >libxft issue #15 > > >fix compil

Re: Build errors at link time - what am I missing?

- Original Message - | From: "Chris Green" | To: "Vile mailing list" | Sent: Wednesday, November 30, 2022 6:42:39 PM | Subject: Re: Build errors at link time - what am I missing? | On Wed, Nov 30, 2022 at 06:32:59PM -0500, Thomas Dickey wrote: |> On Wed, Nov 30, 2

Re: Build errors at link time - what am I missing?

On Wed, Nov 30, 2022 at 08:26:07PM +, Chris Green wrote: > On Wed, Nov 30, 2022 at 08:20:53PM +, Chris Green wrote: > > I'm trying to build vile-9.8 on a Debian system where I have a shared > > hosting account with ssh access. > > > > I'm doing "./configure --prefix=$HOME" and it runs OK

ANN: xterm-377

Files: https://invisible-island.net/archives/xterm/current/xterm-377.tgz https://invisible-island.net/archives/xterm/current/xterm-377.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz.asc

ANN: xterm-377

Files: https://invisible-island.net/archives/xterm/current/xterm-377.tgz https://invisible-island.net/archives/xterm/current/xterm-377.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz.asc

ANN: xterm-376

Files: https://invisible-island.net/archives/xterm/current/xterm-376.tgz https://invisible-island.net/archives/xterm/current/xterm-376.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz.asc

ANN: xterm-376

Files: https://invisible-island.net/archives/xterm/current/xterm-376.tgz https://invisible-island.net/archives/xterm/current/xterm-376.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz.asc

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Wed, Nov 16, 2022 at 04:02:18AM -0500, Thomas Dickey wrote: > On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > > Control: severity -1 minor ... > > After restarting X xterm is starting properly now. It somehow seems > > that the mkfontdir call changed the

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Wed, Nov 16, 2022 at 04:02:18AM -0500, Thomas Dickey wrote: > On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > > Control: severity -1 minor ... > > After restarting X xterm is starting properly now. It somehow seems > > that the mkfontdir call changed the

Re: [ANNOUNCE] libXft 2.3.7

On Tue, Nov 15, 2022 at 03:27:38PM -0500, Thomas E. Dickey wrote: > Thomas E. Dickey (4): > libxft issue #15 > fix compiler warning > libxft issue #16 I hadn't thought of this while committing the changes, but had used short titles because a CI rule limited lines to 80 columns.

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > Control: severity -1 minor > > Hi Thomas, > > at first thanks a lot for your patience. > > Am Tue, Nov 15, 2022 at 08:10:18PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 15, 2022 at 09:15:43AM +0100, An

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > Control: severity -1 minor > > Hi Thomas, > > at first thanks a lot for your patience. > > Am Tue, Nov 15, 2022 at 08:10:18PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 15, 2022 at 09:15:43AM +0100, An

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > Hi again, > > I need to admit that the issue "vanished" on my workhorse laptop which is > nice on one hand but having an explanation would be even nicer. ;-) > I've now tried the other laptop with the same problem: > > $ dpkg

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > Hi again, > > I need to admit that the issue "vanished" on my workhorse laptop which is > nice on one hand but having an explanation would be even nicer. ;-) > I've now tried the other laptop with the same problem: > > $ dpkg

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Mon, Nov 14, 2022 at 06:21:50PM +0100, Andreas Tille wrote: > Am Mon, Nov 14, 2022 at 04:27:30AM -0500 schrieb Thomas Dickey: > > > Since xterm is crashing before this does not report anything > > > interesting. > > > > hmm - it's not showing much. > >

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Mon, Nov 14, 2022 at 06:21:50PM +0100, Andreas Tille wrote: > Am Mon, Nov 14, 2022 at 04:27:30AM -0500 schrieb Thomas Dickey: > > > Since xterm is crashing before this does not report anything > > > interesting. > > > > hmm - it's not showing much. > >

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Mon, Nov 14, 2022 at 09:02:22AM +0100, Andreas Tille wrote: > Am Sun, Nov 13, 2022 at 08:33:09PM -0500 schrieb Thomas Dickey: > > > LANGUAGE= > > > LC_CTYPE="de_DE.UTF-8" > > > LC_NUMERIC="de_DE.UTF-8" > > > LC_TIME="de_DE.UTF-

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Mon, Nov 14, 2022 at 09:02:22AM +0100, Andreas Tille wrote: > Am Sun, Nov 13, 2022 at 08:33:09PM -0500 schrieb Thomas Dickey: > > > LANGUAGE= > > > LC_CTYPE="de_DE.UTF-8" > > > LC_NUMERIC="de_DE.UTF-8" > > > LC_TIME="de_DE.UTF-

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Sat, Nov 12, 2022 at 03:17:01PM +0100, Andreas Tille wrote: > Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > >

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Sat, Nov 12, 2022 at 03:17:01PM +0100, Andreas Tille wrote: > Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > >

Re: Always get two windows when using -c

On Sun, Nov 13, 2022 at 09:55:18PM +, Chris Green wrote: > On Sun, Nov 13, 2022 at 03:40:43PM -0500, Thomas Dickey wrote: > > On Sun, Nov 13, 2022 at 08:11:17PM +, Chris Green wrote: > > > On Sun, Nov 13, 2022 at 10:55:07AM -0500, Thomas Dickey wrote: > > > >

Re: Always get two windows when using -c

On Sun, Nov 13, 2022 at 08:11:17PM +, Chris Green wrote: > On Sun, Nov 13, 2022 at 10:55:07AM -0500, Thomas Dickey wrote: > > On Sun, Nov 13, 2022 at 01:57:30PM +, Chris Green wrote: > > > This relates to my recent posting about trying to use the '-c' command > >

Re: Always get two windows when using -c

On Sun, Nov 13, 2022 at 01:57:30PM +, Chris Green wrote: > This relates to my recent posting about trying to use the '-c' command > line option. However it's now a more general problem/question. > > Whenever I add a '-c command' (or a '+ command', or a '-g NNN') to the > command line vile

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > *VT100.utf8Fonts.font: fixed what locale settings are you usin

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > *VT100.utf8Fonts.font: fixed what locale settings are you usin

Re: [Lynx-dev] colo(u)red figcaptions

On Tue, Nov 01, 2022 at 05:22:40AM -0600, rb...@alumni.caltech.edu wrote: > 'I'd check the diff by using dtd_util to regenerate the header > files.' > dtd_util? WWW/Library/Implementation/dtd_util.c (read the makefile, to see how it is used). -- Thomas E. Dickey

Re: [Lynx-dev] How stable is 2.9.0?

On Tue, Nov 01, 2022 at 07:21:17PM -0400, Travis Siegel wrote: > For what it's worth, I've been using 2.9.0 since version dev 5, and I've not > encountered any major bugs with it.  I'm fairly confident it will be plenty > stable enough for your use. > > It's possible you'll find something else

Re: [Lynx-dev] colo(u)red figcaptions

On Tue, Oct 25, 2022 at 10:37:28PM -0600, rb...@alumni.caltech.edu wrote: > I needed -p0. Here's the patch - do you want me to do > something else? actually, as an attachment would make it easier to extract. given that, I'd check the diff by using dtd_util to regenerate the header files.

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Fri, Oct 28, 2022 at 03:49:52AM -0400, Thomas Dickey wrote: > On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > > Package: xterm > > Version: 375-1 > > Severity: important > > > > Hi, > > > > after upgrading from xterm 374-1 to 37

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Fri, Oct 28, 2022 at 03:49:52AM -0400, Thomas Dickey wrote: > On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > > Package: xterm > > Version: 375-1 > > Severity: important > > > > Hi, > > > > after upgrading from xterm 374-1 to 37

ANN: luit-20221028

Files: https://invisible-island.net/archives/luit/current/luit-2.0.20221028.tgz https://invisible-island.net/archives/luit/current/luit-2.0.20221028.tgz.asc https://invisible-island.net/archives/luit/luit-20221028.tgz https://invisible-island.net/archives/luit/luit-20221028.tgz.asc

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > Package: xterm > Version: 375-1 > Severity: important > > Hi, > > after upgrading from xterm 374-1 to 375-1 I get: > > $ xterm > xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" > Segmentation fault > > I guess this

Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"

On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > Package: xterm > Version: 375-1 > Severity: important > > Hi, > > after upgrading from xterm 374-1 to 375-1 I get: > > $ xterm > xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" > Segmentation fault > > I guess this

Re: [Lynx-dev] colo(u)red figcaptions

On Mon, Oct 24, 2022 at 10:11:35PM -0600, rbell--- via Lynx-dev wrote: > I found my mistake. How do I create a patch? I tried: > > diff -ruN lynx2.9.0dev.10 lynx2.9.0dev.10_patchedforfigcaption > patch > > but it looks different from official patches - and it doesn't work. I use

Re: vile source links

On Sat, Oct 22, 2022 at 01:42:21PM +, Wayne Cuddy via discussions concerning the vile text editor wrote: > On Fri, Oct 21, 2022 at 07:42:01PM -0400, Thomas Dickey wrote: > > On Fri, Oct 21, 2022 at 06:20:40PM +, Wayne Cuddy via discussions > > concerning the vile te

Re: [Lynx-dev] colo(u)red figcaptions

On Fri, Oct 21, 2022 at 08:00:14AM -0600, rbell--- via Lynx-dev wrote: > A patch! Just the thing. I searched for CAPTION in the > source, found it in: > > WWW/Library/Implementation/src1_HTMLDTD.txt > WWW/Library/Implementation/hdr_HTMLDTD.h >

ANN: xterm-375

Files: https://invisible-island.net/archives/xterm/current/xterm-375.tgz https://invisible-island.net/archives/xterm/current/xterm-375.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz.asc

ANN: xterm-375

Files: https://invisible-island.net/archives/xterm/current/xterm-375.tgz https://invisible-island.net/archives/xterm/current/xterm-375.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz.asc

Re: vile source links

On Fri, Oct 21, 2022 at 06:20:40PM +, Wayne Cuddy via discussions concerning the vile text editor wrote: > On the vile download page: > > https://www.invisible-island.net/vile/vile.html#download > > The links for the source downloads: > >

Re: [Lynx-dev] assign or view colors on INS: or DEL: on wikipedia diff page

On Sat, Oct 15, 2022 at 08:21:13AM +, jindam, vani via Lynx-dev wrote: > hello lynx devs, > > i want to assign or view background or > foreground colors for INS: or DEL: on > wikipedia diff page. > > https://en.wikipedia.org/w/index.php?title=Sarai_metro_station=prev=1116048286 > contains

ANN: xterm-374

Files: https://invisible-island.net/archives/xterm/current/xterm-374.tgz https://invisible-island.net/archives/xterm/current/xterm-374.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz.asc

ANN: xterm-374

Files: https://invisible-island.net/archives/xterm/current/xterm-374.tgz https://invisible-island.net/archives/xterm/current/xterm-374.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz.asc

Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1

- Original Message - | From: "Thomas Dickey" | To: 1021...@bugs.debian.org | Cc: 1021243-submit...@bugs.debian.org | Sent: Tuesday, October 4, 2022 8:22:23 PM | Subject: Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1 | On Tue, Oct 04, 2022 at

Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1

- Original Message - | From: "Thomas Dickey" | To: 1021...@bugs.debian.org | Cc: 1021243-submit...@bugs.debian.org | Sent: Tuesday, October 4, 2022 8:22:23 PM | Subject: Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1 | On Tue, Oct 04, 2022 at

Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1

On Tue, Oct 04, 2022 at 11:36:50AM +0200, Emanuele Rocca wrote: > Package: xterm > Version: 373-1 > Severity: important > > Hi, > > the upgrade from xterm 372-1 to 373-1 changes font size on my system. > > See what the fonts used to look like with 372-1 vs 373-1 in the attached > screenshots.

Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1

On Tue, Oct 04, 2022 at 11:36:50AM +0200, Emanuele Rocca wrote: > Package: xterm > Version: 373-1 > Severity: important > > Hi, > > the upgrade from xterm 372-1 to 373-1 changes font size on my system. > > See what the fonts used to look like with 372-1 vs 373-1 in the attached > screenshots.

Re: Yet another leak in Xlib

On Mon, Oct 03, 2022 at 06:47:32PM +0800, Po Lu wrote: > Po Lu writes: > > > ==67186== 408 bytes in 1 blocks are definitely lost in loss record 272 of > > 344 > > ==67186==at 0x484A464: calloc (vg_replace_malloc.c:1328) > > ==67186==by 0x490935F: _XimOpenIM (in

Re: A somewhat off-topic question about ncurses and wrapping long lines

On Sun, Oct 02, 2022 at 09:22:03AM +0100, Chris Green wrote: > On Sat, Oct 01, 2022 at 06:35:26PM -0400, Thomas Dickey wrote: > > On Sat, Oct 01, 2022 at 10:01:00AM +0100, Chris Green wrote: > > > Well it's not entirely off topic, it's about something that works as > > &g

Re: A somewhat off-topic question about ncurses and wrapping long lines

On Sat, Oct 01, 2022 at 10:01:00AM +0100, Chris Green wrote: > Well it's not entirely off topic, it's about something that works as > I'd expect it to in vile (and less) but doesn't work right in mutt (my > E-Mail program of choice). > > The issue is about how long chunks of text, with no spaces

Re: [Lynx-dev] Alert!: Illegal redirection URL received from server! WHEN USING HTTP_PROXY & HTTPS_PROXY

On Wed, Sep 21, 2022 at 12:44:24PM -0400, Philippe Jean wrote: > Thir url > (https://www.google.com/sorry/index?continue=https://www.google.com/search%3Fq%3Dlynx%2520browser%2520configuration%2520file%2520socks5%2520proxy%26num%3D30=EhAgAQZ8JmAEJQAmAANnGMT7rJkGIhAFDhEOM7juXZaTTugEuQScMgFy) >

ANN: xterm-373

Files: https://invisible-island.net/archives/xterm/current/xterm-373.tgz https://invisible-island.net/archives/xterm/current/xterm-373.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz.asc

ANN: xterm-373

Files: https://invisible-island.net/archives/xterm/current/xterm-373.tgz https://invisible-island.net/archives/xterm/current/xterm-373.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz.asc

Re: [Lynx-dev] help

On Sat, Sep 24, 2022 at 11:24:10AM -0400, ww ww wrote: > Using Lynx for DOS... > > it says: "Looking up lynx.browser.org" > > then, "Alert! unable to connect to remote host." > > then, "lynx: Can't access startfile http://lynx.browser.org/; lynx.browser.org appears to be still there (out of

Re: [Lynx-dev] TLS 1.2

On Wed, Sep 21, 2022 at 05:28:55AM +, Wilson Chan via Lynx-dev wrote: > Hi there, > > Hope you are doing fine. > We are currently using Lynx 2.8.7rel.1 (05 Jul 2009). The current stable release is 2.8.8 (July 2018), and the development version is 2.9.0dev.10 (October 2021). > When Lynx

update libXft to 2.3.6

The release monitoring project for libXft (https://release-monitoring.org/project/1777/) doesn't appear to have noticed the release of 2.3.6 a week ago. Any clues on how to fix this? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

[ANNOUNCE] libXft 2.3.6

Adam Sampson (1): Fix length check in XftTextExtents*. Alan Coopersmith (3): Build xz tarballs instead of bzip2 Fix spelling/wording issues gitlab CI: add a basic build test Maxime Coste (3): Introduce a _XftCompositeString helper function Introduce a

[ANNOUNCE] libXft 2.3.6

Adam Sampson (1): Fix length check in XftTextExtents*. Alan Coopersmith (3): Build xz tarballs instead of bzip2 Fix spelling/wording issues gitlab CI: add a basic build test Maxime Coste (3): Introduce a _XftCompositeString helper function Introduce a

[ANNOUNCE] libXft 2.3.5

Alan Coopersmith (3): Build xz tarballs instead of bzip2 Fix spelling/wording issues gitlab CI: add a basic build test Maxime Coste (3): Introduce a _XftCompositeString helper function Introduce a _XftCompositeText helper function Add support for BGRA glyphs

[ANNOUNCE] libXft 2.3.5

Alan Coopersmith (3): Build xz tarballs instead of bzip2 Fix spelling/wording issues gitlab CI: add a basic build test Maxime Coste (3): Introduce a _XftCompositeString helper function Introduce a _XftCompositeText helper function Add support for BGRA glyphs

Re: how to update rpms/vile?

thanks - I'll use this information ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List

how to update rpms/vile?

I'm the upstream developer/maintainer for vile (vi like emacs) and a few other programs packaged in Fedora. The vile rpm is a couple of years out of date, now, and I don't see recent activity by the package maintainer. What can I do to get it moving again? (Earlier this year, I restored a

Re: [Update] editors/vile: 9.8y -> 9.8w

Attached is an update for editors/vile. From 9.8u to 9.8w. Changes are summarized here: https://invisible-island.net/vile/CHANGES.html#v9_8w This update also amends the existing port to work better on OpenBSD: a) use built-in syntax filters, workaround for OpenBSD permissions b) use curses

[Update] editors/vile: 9.8y -> 9.8w

Attached is an update for editors/vile. From 9.8u to 9.8w. Changes are summarized here: https://invisible-island.net/vile/CHANGES.html#v9_8w This update also amends the existing port to work better on OpenBSD: a) use built-in syntax filters, workaround for OpenBSD permissions b) use curses

Re: package/freebsd/*vile content is for 9.8v rather than for 9.8w

On Mon, Aug 22, 2022 at 04:09:17PM -0400, Thomas Dickey wrote: > On Mon, Aug 22, 2022 at 01:48:21PM +0200, Gary Jennejohn wrote: > > I tried to build {,x}vile9.8w for FreeBSD using what's under > > package/freebsd, > > but all the files are for 9.8v. > > >

ANN: vile-9.8w

Files: https://invisible-island.net/archives/vile/current/vile-9.8w.tgz https://invisible-island.net/archives/vile/current/vile-9.8w.tgz.asc https://invisible-island.net/archives/vile/patches/MD5sums https://invisible-island.net/archives/vile/patches/vile-9.8w.patch.gz

Re: Leak in XKeysymToString

On Sat, Aug 20, 2022 at 09:51:42AM -0700, Alan Coopersmith wrote: > Thanks - while gitlab is our preferred method, when that's not possible, > we prefer using the xorg-devel mailing list (cc'ed) instead of trying to > guess which individual developer to contact. > > This bug has been previously

Re: [PATCH] Fix build failure with Perl 5.36

On Tue, Aug 09, 2022 at 06:44:58PM -0700, Kevin Buettner wrote: > On Mon, 4 Jul 2022 15:12:27 +1000 > Brendan O'Dea wrote: > > > Fix a build failure for Perl 5.36 caused by a namespace conflict of > > the symbol `regexp' (http://bugs.debian.org/1014289). > > I've tested this fix on my (Fedora)

Re: [Lynx-dev] lynx blinking after terminal window resizing

On Tue, Aug 02, 2022 at 10:37:46PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >> I see it on Debian stable/bullseye, for example. > > > >I still don't see it with this combination. > > Huh. > > >The blinking that you're describing would

Re: [Lynx-dev] lynx blinking after terminal window resizing

On Mon, Aug 01, 2022 at 10:19:17PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >On Sun, Jun 12, 2022 at 03:16:40AM +0300, mark zaharov wrote: > >> here is the solution which my friend provides. He said it works well with > >> slang and this bug exists

Re: UTF8 has stopped working in vile after OS upgrade

> --bod > > On Sat, 30 Jul 2022 at 00:00, Chris Green wrote: > > > On Fri, Jul 29, 2022 at 04:27:05AM -0400, Thomas Dickey wrote: > > > On Fri, Jul 29, 2022 at 03:40:12PM +1000, Brendan O'Dea wrote: > > > > Testing the vile 9.8v-2 package on my Debian machine I get som

[Ubuntu-x-swat] [Bug 1983276] Re: xterm processing grep color loses char at end of line

If you don't like that, you should (see the FAQ) avoid using Linux console as well. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1983276 Title: xterm processing grep color loses char at end

[Ubuntu-x-swat] [Bug 1983276] Re: xterm processing grep color loses char at end of line

You might find the FAQ helpful: https://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1983276 Title: xterm processing grep color

[Ubuntu-x-swat] [Bug 1983276] Re: xterm processing grep color loses char at end of line

That's not a bug. Here's a cleaned-up demo for 80 columns: echo '-- --\33[01;31m\33[KABCD\33[m\33[KE' See for example https://invisible-island.net/vttest/vttest-wrap.html ** Changed in: xterm (Ubuntu) Status: New

Re: UTF8 has stopped working in vile after OS upgrade

On Fri, Jul 29, 2022 at 04:27:05AM -0400, Thomas Dickey wrote: > On Fri, Jul 29, 2022 at 03:40:12PM +1000, Brendan O'Dea wrote: > > Testing the vile 9.8v-2 package on my Debian machine I get some decidedly > > odd behaviour: > > > > The following sequence: > > &g

Re: [Lynx-dev] lynx blinking after terminal window resizing

On Sun, Jun 12, 2022 at 03:16:40AM +0300, mark zaharov wrote: > here is the solution which my friend provides. He said it works well with > slang and this bug exists for ncurces only. > --- lynx-2.9.0dev.10.orig/src/LYStrings.c 2021-10-24 12:05:19.0 > +0300 > +++

Re: UTF8 has stopped working in vile after OS upgrade

On Fri, Jul 29, 2022 at 03:40:12PM +1000, Brendan O'Dea wrote: > Testing the vile 9.8v-2 package on my Debian machine I get some decidedly > odd behaviour: > > The following sequence: > > l- e' c, > > is rendered in vile as: > > \?A3\?E9\?E7 > > outside of vile, in the same terminal that

Re: UTF8 has stopped working in vile after OS upgrade

On Thu, Jul 28, 2022 at 10:27:05PM +0100, Chris Green wrote: > ... and further, no compose key sequences work in vile 9.8v whereas > they do work in vile 9.8u. > > E.g. I can't enter accented characters using COMPOSE + e + ' (for e > with acute accent) or COMPOSE + c + , (for c with a cedilla).

Re: UTF8 has stopped working in vile after OS upgrade

On Thu, Jul 28, 2022 at 09:21:52PM +0100, Chris Green wrote: > Further information... > > I've built vile 9.7 on this system and pound signs work correctly, if > I build vile 9.8 with the same build environment pound signs don't work. That's a fairly long timespan, since I started 9.8 in 2010.

Re: UTF8 has stopped working in vile after OS upgrade

On Thu, Jul 28, 2022 at 11:54:54AM +0100, Chris Green wrote: > I just upgraded my systems from xubuntu 21.10 to xubuntu 22.04. I don't know about "xubuntu", but Ubuntu 22.04 doesn't seem an improvement. > My UTF8 confiuguration in vile and xvile is broken now. > > Well, entering pound

Bug#31477: #31477 lynx: bookmark file is relative to home dir

The documentation was updated in 2.8.2dev.4, to state .h2 DEFAULT_BOOKMARK_FILE # DEFAULT_BOOKMARK_FILE is the filename used for storing personal bookmarks. # It will be prepended by the user's home directory. # NOTE that a file ending in .html or other suffix

Re: [Lynx-dev] lynx misrenders many valid xhtml5 pages on my site

pages. > > On Mon, Jun 13, 2022 at 1:07 PM Thomas Dickey wrote: > > > > - Original Message - > > | From: "Shlomi Fish" > > | To: "Thomas Dickey" > > | Cc: "lynx-dev" > > | Sent: Monday, June 13, 2022 5:38:43 AM > &

[Lynx-dev] [n...@netguru.com: Cookies, Lynx and the beginnings of the Web – a story worth telling]

-- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net --- Begin Message --- Hello Thomas, I hope you're doing great. We've recently published a story about one of the co-founders of Lynx – Lou Montulli. *You can read the story here.

Bug#1015756: lynx: segfault when setting 'default colors' to 'OFF'

On Wed, Jul 20, 2022 at 06:37:18PM -0400, Thomas Dickey wrote: > On Wed, Jul 20, 2022 at 06:27:34PM -0400, Thomas Dickey wrote: > > On Wed, Jul 20, 2022 at 06:01:01PM -0400, Thomas Dickey wrote: > > > On Wed, Jul 20, 2022 at 05:50:48PM +0200, Cédric Hannotier wrote: >

Bug#1015756: lynx: segfault when setting 'default colors' to 'OFF'

On Wed, Jul 20, 2022 at 06:27:34PM -0400, Thomas Dickey wrote: > On Wed, Jul 20, 2022 at 06:01:01PM -0400, Thomas Dickey wrote: > > On Wed, Jul 20, 2022 at 05:50:48PM +0200, Cédric Hannotier wrote: > > > Package: lynx > > > Version: 2.9.0dev.10-1 > > > Severity:

Bug#1015756: lynx: segfault when setting 'default colors' to 'OFF'

On Wed, Jul 20, 2022 at 06:01:01PM -0400, Thomas Dickey wrote: > On Wed, Jul 20, 2022 at 05:50:48PM +0200, Cédric Hannotier wrote: > > Package: lynx > > Version: 2.9.0dev.10-1 > > Severity: normal > > > > Dear Maintainer, > > > > Seems that togglin

Bug#1015756: lynx: segfault when setting 'default colors' to 'OFF'

On Wed, Jul 20, 2022 at 05:50:48PM +0200, Cédric Hannotier wrote: > Package: lynx > Version: 2.9.0dev.10-1 > Severity: normal > > Dear Maintainer, > > Seems that toggling off the "default colors" in the option menu > crashes lynx (segfault). > > Steps: > - $ lynx > - Press o > - navigate to

Bug#1014625: xterm: screen corruption of scrollback buffer

On Sat, Jul 09, 2022 at 02:39:41PM +1000, Tim Connors wrote: > Package: xterm > Version: 372-1 > Severity: normal > > I'm getting screen corruption (scattered blocks of blackness) over > text in the xterm display when scrolling back. The blocks move with > the contents of the scrollback when

Bug#1014625: xterm: screen corruption of scrollback buffer

On Sat, Jul 09, 2022 at 02:39:41PM +1000, Tim Connors wrote: > Package: xterm > Version: 372-1 > Severity: normal > > I'm getting screen corruption (scattered blocks of blackness) over > text in the xterm display when scrolling back. The blocks move with > the contents of the scrollback when

Re: [PATCH] Fix build failure with Perl 5.36

On Mon, Jul 04, 2022 at 03:12:27PM +1000, Brendan O'Dea wrote: > Fix a build failure for Perl 5.36 caused by a namespace conflict of > the symbol `regexp' (http://bugs.debian.org/1014289). ... I suppose I'll have to put out a 9.8w in the next few weeks, once Perl 5.36 becomes more widespread. In

Re: [PATCH] Remove obsolete gcc pragma

On Mon, Jul 04, 2022 at 02:20:15PM +1000, Brendan O'Dea wrote: > Remove a pragma from perl.xs which gcc no longer recognises. > > This pragma was meant to reduce noise, but now adds more. Compiling > with gcc 11 produces: That's a recent change, from December. My checkin comment says quiet

Bug#1014289: vile: FTBFS with Perl 5.36: ‘regexp_aligned’ undeclared here

On Sun, Jul 03, 2022 at 04:57:01PM +0300, Niko Tyni wrote: > Source: vile > Version: 9.8v-2 > Severity: normal > Tags: ftbfs > User: debian-p...@lists.debian.org > Usertags: perl-5.36-transition > > This package fails to build from source with Perl 5.36 (currently in > experimental). fix

Re: Setting keyboard layout on xterm

On Sat, Jul 02, 2022 at 09:43:25PM +, RVP wrote: > On Sat, 2 Jul 2022, Riza Dindir wrote: > > > Would that mean that uxterm is the same as xterm with the > > configuration that I have done to xterm? > > > > xterm with this resource (and the class set to UXTerm) is functionally > the same as

Re: Setting keyboard layout on xterm

initialization scripts may set a different locale. > And the locale output when running xterm "as is" is > > LANG="" > LC_CTYPE="C" > LC_COLLATE="C" > LC_TIME="C" > LC_NUMERIC="C" > LC_MONETARY="C" >

Re: Setting keyboard layout on xterm

On Thu, Jun 30, 2022 at 11:48:56AM +0300, Valery Ushakov wrote: > On Thu, Jun 30, 2022 at 04:12:37 -0400, Thomas Dickey wrote: > > > "xsrc" is a separate tree - see > > > > http://cvsweb.netbsd.org/bsdweb.cgi/?only_with_tag=MAIN > > > >

Re: Setting keyboard layout on xterm

ons, like firefox, I can, after changing the > keyboard layout (to us, or de, or tr), all the keys produce the > characters as expected. > > Riza > > On Thu, Jun 30, 2022 at 12:11 AM Thomas Dickey wrote: > > > > On Wed, Jun 29, 2022 at 03:20:21PM -0400, Thomas Dickey

Re: Setting keyboard layout on xterm

- Original Message - | From: "Brett Lymn" | To: "Thomas Dickey" | Cc: "Martin Husemann" , "Riza Dindir" , "Netbsd-Users-List" | | Sent: Thursday, June 30, 2022 3:07:00 AM | Subject: Re: Setting keyboard layout on xterm | On Wed, Jun

<    1   2   3   4   5   6   7   8   9   10   >