X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com Message-ID: <20140804185859.19584.qmail@stuge.se> Date: Mon, 4 Aug 2014 20:58:58 +0200 From: Peter Stuge To: geda-help AT delorie DOT com Subject: Re: [geda-help] Having some trouble again! Mail-Followup-To: geda-help AT delorie DOT com References: <53452A49 DOT 8000701 AT mochima DOT com> <20140409114728 DOT GA2172 AT localhost DOT localdomain> <5348800F DOT 3070500 AT mochima DOT com> <201404112358 DOT s3BNwoEw009040 AT envy DOT delorie DOT com> <5348973D DOT 9020603 AT mochima DOT com> <201404120135 DOT s3C1ZVgH012034 AT envy DOT delorie DOT com> <5348B7CE DOT 1070107 AT mochima DOT com> <201404120354 DOT s3C3sNtU018282 AT envy DOT delorie DOT com> <5348BE56 DOT 8000106 AT mochima DOT com> <201404120422 DOT s3C4MPbM020295 AT envy DOT delorie DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201404120422.s3C4MPbM020295@envy.delorie.com> Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk DJ Delorie wrote: > We can't report an error for your case and support the other > use case at the same time. It's not great for software to overload arbitrary meaning to user data. It would be nice to model the U2a U2b case better, such that an error can be reported for Carlos' case. //Peter