From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:bcc0::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id qPYNEvAdZWAE6AAAgWs5BA (envelope-from ) for ; Thu, 01 Apr 2021 03:12:16 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id qH7IC/AdZWDmEQAAbx9fmQ (envelope-from ) for ; Thu, 01 Apr 2021 01:12:16 +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 2E7861DD7E for ; Thu, 1 Apr 2021 03:12:13 +0200 (CEST) Received: from localhost ([::1]:36504 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lRlsZ-0000Yt-T7 for larch@yhetil.org; Wed, 31 Mar 2021 21:12:11 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43896) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lRlsC-0000Yk-9j for emacs-orgmode@gnu.org; Wed, 31 Mar 2021 21:11:48 -0400 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]:34540) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lRlsA-0002fW-G1 for emacs-orgmode@gnu.org; Wed, 31 Mar 2021 21:11:47 -0400 Received: by mail-yb1-xb2e.google.com with SMTP id i144so70012ybg.1 for ; Wed, 31 Mar 2021 18:11:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cDHmV22nU535pGfddFrOhQqPBHPwpZMP7deqGLyzK78=; b=PXBjC20z2wXGmFjmSgrp9WPpbV8jRU+Z7TTqV4WhTCSMF/u+Fzmg+DTpPZa6HmDZxq 8CidAMJSgGRpxwOL7/6yPE0VIVeYXcY5QulIMGwM3ASVhZnllZfS0HHf4mUDCjJx6mZ7 oJLClo3dX1DjGLYw+o6JbsMQgD1Zj6Z/SnRrEXGBKUH+PRimxA93BIt36dUpQTUZmxni Ip0yE2/Ls4Rx59+/puB8wJwBb7DBqztl8aPrh9SBjAWBb8f9COau/qH4dOTYMaGQqM3a 8IyzeFKRPfhOAoR3QH/GXpdMvrY/vSabN+MbvCn6wEQ1MxcpE3Oynwooi58NspHsk4tG +Sfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cDHmV22nU535pGfddFrOhQqPBHPwpZMP7deqGLyzK78=; b=KfFwpfN/Zqkg5/xix+0Tb5E3WQroMbyLGLp2zALDqmY0DYxpKihI0r80eb8fUmEyCO X6m8s0ums+4rsxdEqGZ36ayHlfUTgtHvthrvX/aOz5ir7zoP2YQyUHEDk6qj6tf/+zdZ 3hY97x6Re5Jk7jJ6UMTeNMyWmY0RN8c2izV9vgdig14wYpjZVTFCowqrFeA/ahHOfMps owpteJ6LONm3EyCHQfqiLBjbhav2dHjOXSVdTAna+8RDKndKHZFWZwRhBwrxB9mmd5PO psYv3UaeTsiI5nHafmyUBY36UIf3JZbQnDKzvzQdjYowcb/f+OZIfEGRc8aXzUD7s6qV ZFIQ== X-Gm-Message-State: AOAM532yfM+dxxcLOml9s78BNZ/r4NcxE41Q9ijUNCHFaRo/azKlKQjG IA7Gj4i2MlY80SG+/b3DNApU8MWFxcZcGTXHEPI= X-Google-Smtp-Source: ABdhPJwUhhe+VLQK7VWAA0Chd6utuoMoIfisITEU1m/F6PWkxHqcmAwIXWaHMJ31XmZabSn08I0jLqG/lfp/VcsojZw= X-Received: by 2002:a25:aa0b:: with SMTP id s11mr7895286ybi.147.1617239504378; Wed, 31 Mar 2021 18:11:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bill Burdick Date: Wed, 31 Mar 2021 20:11:33 -0500 Message-ID: Subject: Re: Using backticks for the inline code delimeter? To: gmauer@gmail.com Content-Type: multipart/alternative; boundary="0000000000002cdedc05bedeea99" Received-SPF: pass client-ip=2607:f8b0:4864:20::b2e; envelope-from=bill.burdick@gmail.com; helo=mail-yb1-xb2e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_FROM=0.001, HTML_MESSAGE=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: , Cc: emacs-orgmode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1617239534; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=cDHmV22nU535pGfddFrOhQqPBHPwpZMP7deqGLyzK78=; b=O2h8nJEhFE+YeOxOE4iH+BWcN9423oJjRfhG3fcTsvjZwh1MOJeK7JHeEvcTaURv9u98DE DMUT2u2Dxacp9FVdVqyc+fXXXRuCSsj+7uHWAkjYT1IjdS5uTgiwvQY+wMkrPDSiyY/RKK jiJ+CdDSG3wG7puWsU5/QPiPpsV/Cl9EFxUWGDqR0dAIPkMuWGMLRaG7l/ADLKsN89Y1uP lsVa7YM2Mxsym6IGRJIFkedGS/azVyxA+Gzz1vS+HA3B2VDZ4Vpo5sYT37JcbUwrbXGn1N PC6g/UBHRhKj4hj7JWcFYn031SxOPSSbzpqXWPES7F/C5U0aWxunmpHOuO+ZIw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1617239534; a=rsa-sha256; cv=none; b=lJW0RcAnOwFlfXAYED4PBfGQc48b+wmbIg9kDjrUgqfAQfjdPTGGpXY3fdVif2evdM/6sM kTjdkp3E3aeNyUJFvypNy4Nu18IQboQ7l9KlGWJyGoJRhNTBPfl05ZCR+BfU26TQDbBv6f jWk8QURh+sd6/0EvePSeZ9kARw4hx5uXobWza5O0CoQhVDEpaqqmDKEaq/VAL+rWC59Pr5 BlWP6pWaZefFfmhJk/o7ci7Uf16npkFI3s1awVL0ryY9vjkNao9PjO4vxtba+/ztpWQU9n DeaNZk8oVrD9cJp+7KZn6/XahuGXEYEW+zo2i/OG87t/5rRFmJgU5s/Ub//00A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=PXBjC20z; 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-Spam-Score: -2.13 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=PXBjC20z; 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: 2E7861DD7E X-Spam-Score: -2.13 X-Migadu-Scanner: scn0.migadu.com X-TUID: bSgDaGClZTPk --0000000000002cdedc05bedeea99 Content-Type: text/plain; charset="UTF-8" Grepping for src_ in *.el in the org distro shows 11 hits over 3 files: ob-core.el, ob-exp.el, and org-element.el. That's where you can start working if you want to copy those functions into your init files and modify them for yourself, or you can see if maybe using function advice is sufficient. It's your emacs config, you can modify it however you want, if what you want is to write the code yourself. If you want someone else to write the code for you, however, you'll have to convince someone to do it. If you want someone else to write the code for you and also adopt it into the main distro, that's an even tougher task... -- Bill On Wed, Mar 31, 2021 at 1:50 PM George Mauer wrote: > Markdown uses backticks to denote inline code which should get special > (typically monospace) formatting, org uses the tilde character. > > Now I know that org is not markdown, is far more powerful than markdown, > and is not (mostly) the same use cases as markdown. But this one use case > *does* overlap. And the backticks thing is becoming so ingrained that not > only do I reach for it all the time, but I've seen it crop up on this very > mailing list and even in some README.org documents. > > I would like to submit that org consider adopting backticks as an > alternate way of denoting inline code. > > Aside from any official movement, I would like to add this to my own files > - is there a straightforward way to extend the org parser to do this? > --0000000000002cdedc05bedeea99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Grepping for src_ in *.el in the org distro shows 11 = hits over 3 files: ob-core.el, ob-exp.el, and org-element.el. That's wh= ere you can start working if you want to copy those functions into your ini= t files and modify them for yourself, or you can see if maybe using functio= n advice is sufficient.

It's your emacs c= onfig, you can modify it however you want, if what you want is to write the= code yourself.


If you want someone else to write the code for you, however, you&#= 39;ll have to convince someone to do it.

If you wa= nt someone else to write the code for you and also adopt it into=C2=A0the m= ain distro, that's an even tougher task...

-- Bill

=

= On Wed, Mar 31, 2021 at 1:50 PM George Mauer <gmauer@gmail.com> wrote:
Markdown uses backticks to = denote inline code which should get special (typically monospace) formattin= g, org uses the tilde character.

Now I know that o= rg is not markdown, is far more powerful than markdown, and is not (mostly)= the same use cases as markdown. But this one use case *does* overlap. And = the backticks thing is becoming so ingrained that not only do I reach for i= t all the time, but I've seen it crop up on this very mailing list and = even in some README.org documents.

I would like to= submit that org consider adopting backticks as an alternate way of denotin= g=C2=A0inline code.=C2=A0

Aside from any official = movement, I would like to add this to my own files - is there a straightfor= ward way to extend the org parser to do this?
--0000000000002cdedc05bedeea99--