From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Hikaru Ichijyo Newsgroups: gmane.emacs.help Subject: Re: logical not condition in ibuffer config Date: Mon, 12 Mar 2018 00:17:15 -0500 Organization: UN Spacy Message-ID: <8xxbmft27qc.fsf@macross.sdf.jp> References: <8xxk1ui1i4v.fsf@macross.sdf.jp> <864llmz77w.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1520831914 32215 195.159.176.226 (12 Mar 2018 05:18:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Mar 2018 05:18:34 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Mar 12 06:18:30 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1evFqw-0008Ei-8P for geh-help-gnu-emacs@m.gmane.org; Mon, 12 Mar 2018 06:18:30 +0100 Original-Received: from localhost ([::1]:56690 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evFsx-00044i-80 for geh-help-gnu-emacs@m.gmane.org; Mon, 12 Mar 2018 01:20:35 -0400 X-Received: by 10.55.52.85 with SMTP id b82mr4971149qka.12.1520831835587; Sun, 11 Mar 2018 22:17:15 -0700 (PDT) Original-Path: usenet.stanford.edu!t24no2790604qtn.0!news-out.google.com!a13ni958qtd.1!nntp.google.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post02.iad!fx13.iad.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Cancel-Lock: sha1:riNYeIKUwD29P9vkUyrpsHMGtOo= Original-Lines: 32 Original-X-Complaints-To: http://abuse.usenetxs.com Original-NNTP-Posting-Date: Mon, 12 Mar 2018 05:17:15 UTC X-Received-Bytes: 1818 X-Received-Body-CRC: 4200173864 Original-Xref: usenet.stanford.edu gnu.emacs.help:222057 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:116175 Archived-At: Emanuel Berg writes: > This is not exactly Lisp but rather a common > computer data hierarchy that is expressed as > list and then parsed as configuration data by > the Lisp program... whatever. > > The easiest way to do what you want is probably > to find out the priority *order* by which the > data structure gets traversed. > > Then, first put the general case (all Elisp) > somewhere, only after that explicitly put the > exception/the specific case (bbdb) wherever you > want it instead, so that rule overwrites the > general case rule (which otherwise applies to > both cases). > > By the way, this level of perfectionism... > start digging into Elisp today as it'll just > get worse. It sounds like you're explaining the algorithm. I understand that. I need to know why Elisp will understand "or" operators in an ibuffer configuration but not "and" or "not"...or suggestions of how "and" or "not" could be coded that would work. -- He that would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty, he establishes a precedent that will reach to himself. --Thomas Paine