Re: colorls in base

New features schould be on by default, why else would we import them? > Am 17.02.2019 um 20:57 schrieb David Holland : > > On Sun, Feb 17, 2019 at 01:24:09PM -0600, Jonathan A. Kollasch wrote: >>> Can we, however, please have colors that are not angry fruit salad? My >>> understanding is that

Re: colorls in base

> Am 15.02.2019 um 21:47 schrieb Kamil Rytarowski : > > On 15.02.2019 17:58, Christian Groessler wrote: >> On 2/15/19 3:20 PM, Christos Zoulas wrote: >>> The kernel is already using green, and recently we added >>> "autoconfiguration >>> error" to highlight errors. Shouldn't we (in addition)

Re: Lua shared object asymmetry loading Xlib.

> Am 20.01.2019 um 11:14 schrieb Kamil Rytarowski : > > On 20.01.2019 11:03, Martin Husemann wrote: >> On Sun, Jan 20, 2019 at 10:32:43AM +0100, Kamil Rytarowski wrote: >>> I find it as workaround of our libc behavior. >> >> I disagree, there is no clean way to implement the call-on-dlclose

Re: Lua shared object asymmetry loading Xlib.

> Am 20.01.2019 um 10:14 schrieb Martin Husemann : > > On Sun, Jan 20, 2019 at 10:06:33AM +0100, Marc Balmer wrote: >> Why are atexit handlers run after dlclosing loaded libraries? That sounds >> wrong to me, but is there a reason? > > They are run at ex

Re: Lua shared object asymmetry loading Xlib.

> Am 04.01.2019 um 19:29 schrieb Valery Ushakov : > > On Wed, Dec 26, 2018 at 09:44:53 -0900, Phil Rulon wrote: > >> msd$ /usr/bin/lua -v test.lua >> Lua 5.3.3 Copyright (C) 1994-2016 Lua.org, PUC-Rio >> table >> function >> [1] Segmentation fault (core dumped) /usr/bin/lua -v test.lua >>

Re: Moving telnet/telnetd from base to pkgsrc

> Am 17.12.2018 um 08:57 schrieb Martin Husemann : > > On Sat, Dec 15, 2018 at 10:43:14PM +0100, Marc Balmer wrote: >> To me it looks like one or two people don't like telnet and have become >> very vocal and loud about removing it and did not invest a lot of thought >

Re: Moving telnet/telnetd from base to pkgsrc

> Am 15.12.2018 um 23:20 schrieb Alexander Nasonov : > > Taylor R Campbell wrote: >> I know English may not be your first language, so here's a couple of >> dictionary entries if you would like to read further: >> >> https://en.wiktionary.org/wiki/name-calling >>

Re: Moving telnet/telnetd from base to pkgsrc

> Am 15.12.2018 um 23:17 schrieb Alexander Nasonov : > > Taylor R Campbell wrote: >> One of the implications at the moment is that anyone on the internet >> between you and the remote host can crash your telnet client[*] with >> no user interaction beyond making a connection. > > Index:

Re: Moving telnet/telnetd from base to pkgsrc

Am 15.12.2018 um 23:15 schrieb Taylor R Campbell : >> Date: Sat, 15 Dec 2018 22:54:05 +0100 >> From: Marc Balmer >> >> Am 15.12.2018 um 22:52 schrieb Taylor R Campbell >> : >> >>>> Date: Sat, 15 Dec 2018 22:43:14 +0100 >>>>

Re: Moving telnet/telnetd from base to pkgsrc

Am 15.12.2018 um 23:08 schrieb Taylor R Campbell : >> Date: Sat, 15 Dec 2018 22:38:10 +0100 >> From: Anders Magnusson >> >> I'm pretty sure that all users of telnet know what the implications >> are. If they don't then it doesn't matter whether it is in base or not. > > One of the

Re: Moving telnet/telnetd from base to pkgsrc

Am 15.12.2018 um 22:52 schrieb Taylor R Campbell : >> Date: Sat, 15 Dec 2018 22:43:14 +0100 >> From: Marc Balmer >> >> To me it looks like one or two people don't like telnet and >> have become very vocal and loud about removing it and did not invest >&

Re: Moving telnet/telnetd from base to pkgsrc

> Am 15.12.2018 um 22:38 schrieb Anders Magnusson : > >> Den 2018-12-15 kl. 22:11, skrev Marc Balmer: >> Whatever. >> >> Please keep telnet and telnetd in base. They have their valid use cases. >> > Yes please. I have used both kerberized te

Re: Moving telnet/telnetd from base to pkgsrc

Is telnet / telnetd less of a risk to our users if it is in pkgsrc rather than in base? Is pkgsrc the toilet for software you don‘t want to see in base? Is pkgsrc your personal toilet? I have good use for telnet and telnetd. I don‘t want it to be removed from base. -mb

Re: unix(3lua)

ling lists > in the past but I can't find anything at the moment. > > Marc, what were your arguments for not using luaposix when you wrote > your module? > > I could only find this message: > > Date: Fri, 19 Dec 2014 09:39:01 +0100 > From: Marc Balmer > To: Lua mailing list

Re: unix(3lua)

> Am 19.05.2018 um 13:43 schrieb Sevan Janiyan <ventur...@geeklan.co.uk>: > > Hi Marc, > > On 17/05/2018 14:48, Marc Balmer wrote: >> If the license (3-clause) is of concern, it can be changed to >> whatever is preferred. > > That's great. Is it pos

Re: unix(3lua)

> Am 19.05.2018 um 13:25 schrieb Sevan Janiyan : > > On 19/05/2018 11:36, Alexander Nasonov wrote: >> The main page of the repository says it's incomplete. > > "This module does not aim to be complete, it merely contains functions > that I needed at some point of time"

Re: unix(3lua)

> Am 19.05.2018 um 12:36 schrieb Alexander Nasonov : > > Sevan Janiyan wrote: >> Hello, >> There is a unixlua[1] module which is a Lua binding for some the >> functions in our C libraries in base as well as system calls. The code >> base is small and doesn't have any tentacles

Re: unix(3lua)

> Am 17.05.2018 um 13:55 schrieb Sevan Janiyan : > > Hello, > There is a unixlua[1] module which is a Lua binding for some the > functions in our C libraries in base as well as system calls. The code > base is small and doesn't have any tentacles (a hand full of C

Re: unix(3lua)

e, because without such a module, you can not write real software in Lua. Lua's own "os" module is limited to what ANSI C provides, which is not really much. > Am 17.05.2018 um 15:37 schrieb Marc Balmer <mhbal...@gmail.com>: > > This belongs into base because i

Re: Default PAGER -> less

> Am 10.09.2017 um 08:25 schrieb Robert Elz : > > You can just set your PAGER to be less, in your private startup > files, and change nothing else, right? > > This is one of those "which do you prefer x or y...?" type questions that > has no right answer. Imo, It is about

Re: On updating Lua

Am 01.09.16 um 16:57 schrieb Taylor R Campbell: >Date: Thu, 1 Sep 2016 13:59:49 +0200 >From: Marc Balmer <m...@msys.ch> > >Would it speed up thinks if we just applied the diffs from PUC Rio >and commiting them, leaving out the vendor import dance? Wou

Re: Initial attempt at a Lua interface to npf(3)

Christian, Am 11.08.14 um 02:26 schrieb Christian Koch: > On Sun, Aug 10, 2014 at 08:11:20PM +0100, Mindaugas Rasiukevicius wrote: >> Christian Koch wrote: >>> Hey everybody, >>> >>> I announced this a little earlier in #netbsd on Freenode, but I've just >>> published an

On updating Lua

Lourival, Guilherme (CCing tech-userlevel@) In the past we updated Lua by doing a vendor import and reapplying our patches. It's doable, but as you have seen, cvs makes that stuff not strictly easy... Furthermore I think that we always lack behind, Lua 5.3.3 with 3 bug fixes applied would be

Re: A Web Interface for Apropos: http://man-k.org

> Am 10.04.2016 um 20:15 schrieb Abhinav Upadhyay > : > > Hi All, > > I have been working on a web interface for apropos(1) and wanted to > share it with all of you: http://man-k.org > > There are still plenty of things to be done but I would appreciate any >