From owner-freebsd-hackers Fri Sep 12 09:41:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16203 for hackers-outgoing; Fri, 12 Sep 1997 09:41:01 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16195 for ; Fri, 12 Sep 1997 09:40:57 -0700 (PDT) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id JAA22697; Fri, 12 Sep 1997 09:40:47 -0700 (PDT) Date: Fri, 12 Sep 1997 09:40:47 -0700 (PDT) From: "Eric J. Schwertfeger" To: Sebastian Lederer cc: Charlie & , hackers@FreeBSD.ORG Subject: Re: Do you have some neat configuration files? In-Reply-To: <34190B2D.326A3F27@bonn-online.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997, Sebastian Lederer wrote: > A problem with window manager configuration files could be that most of them > contain menu definitions for starting applications, and usually 90% of the > menu entries will point to applications which are not installed. That would > be quite frustrating for newbies if they try out the menus and absolutely > nothing happen, not even an error message. So at least from that point of > view, the configuration files should be quite minimal, maybe with lots of > commented out entries for "common" applications. Well, I'm sure there are > people who think quite the opposite... How about extending the config files to allow for "if this file doesn't exist, ignore this line", or "if this file isn't in the path, ignore this line." Done properly, it would only cause minor code bloat, and a little extra work at start/restart time.