From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilya Shlyakhter Subject: Re: case sensitivity Date: Sat, 24 Mar 2012 12:07:58 -0400 Message-ID: References: <87ehsifpst.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBTVj-0007GR-3G for emacs-orgmode@gnu.org; Sat, 24 Mar 2012 12:08:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SBTVh-0005pN-FU for emacs-orgmode@gnu.org; Sat, 24 Mar 2012 12:08:10 -0400 Received: from plane.gmane.org ([80.91.229.3]:52195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBTVh-0005o1-8L for emacs-orgmode@gnu.org; Sat, 24 Mar 2012 12:08:09 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SBTVf-0006vg-Sh for emacs-orgmode@gnu.org; Sat, 24 Mar 2012 17:08:07 +0100 Received: from pool-74-104-46-82.bstnma.east.verizon.net ([74.104.46.82]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 24 Mar 2012 17:08:07 +0100 Received: from ilya_shl by pool-74-104-46-82.bstnma.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 24 Mar 2012 17:08:07 +0100 In-Reply-To: <87ehsifpst.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On 3/24/2012 2:58 AM, Bastien wrote: >> How should case-sensitivity work in Org? The documentation doesn't >> specify. From past messages, it looks like tags and todo keywords >> are defined to be case-sensitive. What about priorities, categories, >> user-defined properties, regexp matching of entries, following of >> links-to-headlines? Other cases? > If there is an issue with a syntactic element being case-(in)sensitive > while (1) it should not and/or (2) docs suggests otherwise, then let's > tackle the problem. Problem is, docs are cleverly silent on the issue :) So for one, it would be good if the docs specified it one way or the other at least in the above cases. But also in the code, case-fold-search is sometimes explicitly set before testing regexps and sometimes isn't. I started fixing this, then realized that there is no spec for the right behavior. So I thought I'd check with the list first. ilya