From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id SLYTL1LcZGAyYAAAgWs5BA (envelope-from ) for ; Wed, 31 Mar 2021 22:32:18 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id IEIGKVLcZGBeLgAA1q6Kng (envelope-from ) for ; Wed, 31 Mar 2021 20:32:18 +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 1F83C131A0 for ; Wed, 31 Mar 2021 22:32:18 +0200 (CEST) Received: from localhost ([::1]:44560 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lRhVg-0001Bl-2C for larch@yhetil.org; Wed, 31 Mar 2021 16:32:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lRhUs-0001BA-SP for emacs-orgmode@gnu.org; Wed, 31 Mar 2021 16:31:30 -0400 Received: from mail-wr1-x42f.google.com ([2a00:1450:4864:20::42f]:41725) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lRhUq-0004eq-Aj for emacs-orgmode@gnu.org; Wed, 31 Mar 2021 16:31:26 -0400 Received: by mail-wr1-x42f.google.com with SMTP id b9so20898721wrt.8 for ; Wed, 31 Mar 2021 13:31:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zzamboni-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dj3Z5AbqSI9EKdkTtrOBwRvexCaFLTqnHngiCswK0ds=; b=l639+EE3XyEpYRc0Cq9XFMLPMj5CI2Kee+L/nOJY4PrOwfz6+z0nBbSMc8tSmygyRx 8juA7cCFba9kV9AKuzNcQxhUKgcZimTWq9P7AHas31wu6kIWjTf7Z2ORy20Wu8amgC7F cf3981r6K5N6IH4jFj3bVL0944dEky2KQN5OxSFywF3C1Ilq/8NbkoKQM0HrdeMIAXEn anTANKzgVcg/n2kO+XZx2uhQfnijJlxxctvs0yM44PaPDX4ltO532M18pRKaXplLDYUH eRF3JRm1ydVyyeSMrlmtMGlzXqHU46kyuJ13qfOhlUc99i5ueuLFEL9Qoxf9GD+BfiEd PmMQ== 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=dj3Z5AbqSI9EKdkTtrOBwRvexCaFLTqnHngiCswK0ds=; b=mMZYNfSN0A9Ct6L1gYiYAXxI6gbXAKvSyVv4EUo9JoFCGTX06Xub3h4ldfyBua4FhJ VSCnnQIoIpt5T6uSOgmNyiNAtHe+GdFU2M6LKS6GKYuv7rEBt+lpwOz9+FzqrzkI1Kny occ926KLYQmPzeVbmZ4NxVgfBGotGJ/f0KNsXx1lF0hTDAuBHQqlPYXw65v5AR7UlH+B BbIncoSIoHEimC4CTs69yvE3OJ8Xgbj+0P53WZ6y1PtzACjxrCB3UsvCyk3U7ZLhgUuR CZ9I3XT76yEJhva/7aEtr3N7feDiOdJMJ9vnY5WhN3C8o8uy3hQp6elFfDiik0wEGUxV kVug== X-Gm-Message-State: AOAM532rXG1mtUJbw/1JxbosIwV/lNcS49kRSiqoqEYU98ushll1xIiZ L+SkuDyXvI+tpMXIY4p9ImsAxxNG3krlNl8d/jNOtA== X-Google-Smtp-Source: ABdhPJxgBY3igkCrTbJeMGa3N0/GXm0xb3mk3WzUk3UbLnZ10CvUhSC3Q4DbeC8PzyA3eQirCpKaFL7fYL5utEwSSJs= X-Received: by 2002:adf:edc3:: with SMTP id v3mr5454934wro.79.1617222680641; Wed, 31 Mar 2021 13:31:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Diego Zamboni Date: Wed, 31 Mar 2021 22:31:09 +0200 Message-ID: Subject: Re: Using backticks for the inline code delimeter? To: gmauer@gmail.com Content-Type: multipart/alternative; boundary="00000000000067280f05bedaff87" Received-SPF: none client-ip=2a00:1450:4864:20::42f; envelope-from=diego@zzamboni.org; helo=mail-wr1-x42f.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=1617222738; 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=dj3Z5AbqSI9EKdkTtrOBwRvexCaFLTqnHngiCswK0ds=; b=fP6JoClKB9XoB97n/2ZO7cSyezPnbNLv/MpHq4m6RK1GBhj/PNFbKyG5xs0DGB+shXPAA1 Kb85GEL8RwBxxEtRgRzDK2yOANz8TDg2Sfv+LJqwUw0/UkzoiO/vgemjzy+H+LLZo5jj8O DSRP307l3D0siJGd8Gdt/AChA8v84fxembQ6azaDW6X+y4z4Yt+i++fNWQCZSu6OdrV+TM XEXFiRkP4CYAdDIHCbuHf6d+c/b6cwNdloPfPiLNAaG/Js9YgY4R5r8srGfJdSjUP5EVZW IKkh+Qec/EVvPtNV5chPIQayqPyMERjZcPzRKp+RN9VWLLcOP8zIt26jCXcXFw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1617222738; a=rsa-sha256; cv=none; b=N/5uqsbI6v/0VV2fLm8r2JzPJQ3pn5FmXK9ayj9v0k+aNGnIqt1qro7ovty5kaLmXJtTmY jSCeAKHKoBOuLhr8VNUP7ZbPMJiJVZ70XiruwmrVLXQPrc2NI3IaxJNj39hDU0fqRWGr1h VLJyd2tu6rJrZKR3ogLSeoRsuE5ykNBcpOf4niYuebuVHBaBDLdI6oM0t9wiOg0f7mT3C9 ENCHn0qv40noRUWpyWt62kMN7Rc4v9cRoPzvlbMC2kpjLN0mtFcp6d6p8IdoWmbqUhFxMn Y9wmnGzj2U9cYZiDNF9ZxTljC2YgaKB4/SbETHCxfONs6D9MgkXFk5dQQTdbHw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=zzamboni-org.20150623.gappssmtp.com header.s=20150623 header.b=l639+EE3; dmarc=none; 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: -1.63 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=zzamboni-org.20150623.gappssmtp.com header.s=20150623 header.b=l639+EE3; dmarc=none; 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: 1F83C131A0 X-Spam-Score: -1.63 X-Migadu-Scanner: scn0.migadu.com X-TUID: iBYmtSMBtixV --00000000000067280f05bedaff87 Content-Type: text/plain; charset="UTF-8" The approach I've taken is to try and stop using Markdown altogether and write everything in Org, exporting to Markdown for those destinations that need it. You could even use https://github.com/tecosaur/org-pandoc-import to automatically convert/reconvert other formats as needed, and https://github.com/tecosaur/emacs-everywhere to do it even in other applications. It's not perfect - I still have to type Markdown sometimes, but you can eventually start losing the ingrained backtick habit :) --Diego On Wed, Mar 31, 2021 at 8:49 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? > --00000000000067280f05bedaff87 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The=C2=A0approach I've taken is to try and stop u= sing Markdown altogether and write everything in Org, exporting to Markdown= for those destinations that need it.

You could ev= en use=C2=A0https= ://github.com/tecosaur/org-pandoc-import to automatically convert/recon= vert other formats as needed, and=C2=A0https://github.com/tecosaur/emacs-everywhere to do= it even in other applications.

It's not perfe= ct - I still have to type Markdown sometimes, but you can=C2=A0eventually s= tart losing the ingrained backtick habit :)=C2=A0

= --Diego



<= div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 31, 2021 at 8:49 PM George= Mauer <gmauer@gmail.com> wro= te:
Markdown uses backticks to denote inline code which should get sp= ecial (typically monospace) formatting, org uses the tilde character.
=

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

I would like to submit that org consider adopting bac= kticks as an alternate way of denoting=C2=A0inline code.=C2=A0
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 d= o this?
--00000000000067280f05bedaff87--