From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id gTE3DpIC5F/XZgAA0tVLHw (envelope-from ) for ; Thu, 24 Dec 2020 02:53:06 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id us9GBJIC5F+lcwAAbx9fmQ (envelope-from ) for ; Thu, 24 Dec 2020 02:53:06 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 702DD9401BF for ; Thu, 24 Dec 2020 02:53:05 +0000 (UTC) Received: from localhost ([::1]:59330 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ksGkR-0003fK-53 for larch@yhetil.org; Wed, 23 Dec 2020 21:53:03 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:59110) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ksGjh-0003ex-7o for emacs-orgmode@gnu.org; Wed, 23 Dec 2020 21:52:17 -0500 Received: from mail-pg1-x529.google.com ([2607:f8b0:4864:20::529]:45815) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ksGjf-0003sB-JR for emacs-orgmode@gnu.org; Wed, 23 Dec 2020 21:52:17 -0500 Received: by mail-pg1-x529.google.com with SMTP id v19so731689pgj.12 for ; Wed, 23 Dec 2020 18:52:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version :content-transfer-encoding; bh=QX/tRX2Htf6v1XyEeDJilXFEhsVgyuVaFeAeMKt+oDQ=; b=OwqMF69NRYj7yZS00RypbmcoPf9014t4FAYKn/4i3gYwyzZ2x2AugIDdRcWx2KfWDh c8r3X4qv7Dh6UB3vv4xzaB9fuBFibFTiteQJToRFBkxmGadQowayB1KSuITSQB2Mcc+V wleLMW8i6AIsT2g9HvZtcrAuNJbLf0NiMGuKsGctYPYUBCCww6sZt9Ghxwbz8VFKUkfm b0I1vqov6VwHxn416dsTRa/0m3Q00bWRWrIxj0oy0NhsaRZJL+rmxHR+G36NkD0hBkem 3ZDl+O4ZW7H3lQj1aHHru6HG5VsvDNpfI2PK0ZS5ZzmiQ+ZmYxbX3zxgF0k7/UHcOmeh SKig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=QX/tRX2Htf6v1XyEeDJilXFEhsVgyuVaFeAeMKt+oDQ=; b=qyBu8L0C3MnqGNah0Tv5cMKHVHoyugeKIwJhZ34abTnJuozu1KtJ3JGIxOtEOookdZ mUFrhxDYBZ+QMdN/xTaJkC99l4sed5g6zL1kh3rA3O27jntLMmGLGHneYSzZ9iJjc86C tHe5DhFhXf8+2mFIHoLrtifhq3vkLwSA8Fk8EEDqn5xdlvCcoACVk7tiW/EKKDGU4ji1 WA5vxDnJ2YNLn7JCDLSl6Q7opyuA3tcCYZu+dd6tL4+ljACSHlZ8stvxYS7SD4fwa2nB l+wyWHx7Y0lTlxfQk2v84tLOO1IwVfHjl7mCRR7g9coMDOt/E5uFYO8eRGezBSGYM8S9 09vQ== X-Gm-Message-State: AOAM5308+yytBkZo8Qjdq/a8czlc2iWULoLCclfSWYvlyWwnH+RXb1FI uOqP3Q/uzdYps4rEs0wZ4/ff6yk/mAWgdw== X-Google-Smtp-Source: ABdhPJzdNysyOPDUkUp+s0wtZyziWBU0fSf0fcDqTQOOwgZOMOGESctC6mQnSJgSs+FU3k+/rdw/fw== X-Received: by 2002:a63:34d:: with SMTP id 74mr26757721pgd.388.1608778333620; Wed, 23 Dec 2020 18:52:13 -0800 (PST) Received: from localhost ([50.7.251.66]) by smtp.gmail.com with ESMTPSA id m4sm992731pgv.16.2020.12.23.18.52.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Dec 2020 18:52:12 -0800 (PST) From: Ihor Radchenko To: "Victor A. Stoichita" , emacs-orgmode@gnu.org Subject: Re: strange behavior of @ in tag searches In-Reply-To: <87r1ngizs9.fsf@svictor.net> References: <87mty89kvy.fsf@svictor.net> <87pn34rscc.fsf@svictor.net> <8735zz4yn7.fsf@localhost> <87lfdph4cl.fsf@kyleam.com> <87ft3x1klb.fsf@localhost> <87r1ngizs9.fsf@svictor.net> Date: Thu, 24 Dec 2020 10:56:09 +0800 Message-ID: <87y2hnzzcm.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::529; envelope-from=yantar92@gmail.com; helo=mail-pg1-x529.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.53 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=OwqMF69N; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 702DD9401BF X-Spam-Score: -2.53 X-Migadu-Scanner: scn1.migadu.com X-TUID: ybCvpd7IIKmG "Victor A. Stoichita" writes: > I modify the syntax table for text modes to handle the meaning of=20 > some characters in French. In fact, te actual modification doesn=E2=80=99= t=20 > seem to matter. The following is enough to trigger the described=20 > behavior: > > --8<---------------cut here---------------start------------->8--- > (add-hook 'text-mode-hook (lambda () > (set-syntax-table (make-syntax-table)))) > --8<---------------cut here---------------end--------------->8--- That basically clears _all_ syntax settings in org-mode. It would interfere with pretty much any major mode that modifies syntax tables... A better way to modify syntax table is using modify-syntax-entry or you need to make sure that your code inherits org-mode-syntax-table instead of creating an empty table. I just searched through org code and the following syntax table elements are being used by org: -*- mode: helm-grep -*- AG Results for `modify-syntax-entry': org-element.el:380: (modify-syntax-entry ?\( "()" table) org-element.el:381: (modify-syntax-entry ?\) ")(" table) org-element.el:383: (modify-syntax-entry char " " table))) org-element.el:389: (modify-syntax-entry ?\[ "(]" table) org-element.el:390: (modify-syntax-entry ?\] ")[" table) org-element.el:392: (modify-syntax-entry char " " table))) org-element.el:398: (modify-syntax-entry ?\{ "(}" table) org-element.el:399: (modify-syntax-entry ?\} "){" table) org-element.el:401: (modify-syntax-entry char " " table))) ox.el:6870: (modify-syntax-entry ?\[ "w")) org.el:4719: (modify-syntax-entry ?\" "\"") org.el:4720: (modify-syntax-entry ?\\ "_") org.el:4721: (modify-syntax-entry ?~ "_") org.el:4722: (modify-syntax-entry ?< "(>") org.el:4723: (modify-syntax-entry ?> ")<") org.el:4838: (modify-syntax-entry (string-to-char (car c)) "w p" st)))) org.el:10927: (modify-syntax-entry ?@ "w" tag-syntax) org.el:10928: (modify-syntax-entry ?_ "w" tag-syntax) The last two refer to tag groups. > For now, I changed my tags to not use @ any more. > Are there other aspects that I might miss if I alter the syntax=20 > table on =E2=80=99text-mode-hook? I hope the above helps. Best, Ihor