From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Common keybindings idea for multiple markups Date: Sun, 12 Jun 2022 23:07:18 +0300 Message-ID: References: <83o7z47m7y.fsf@gnu.org> <8735gfs3is.fsf@localhost> <838rq75jhg.fsf@gnu.org> <87fskfqj97.fsf@localhost> <83zgin3zcm.fsf@gnu.org> <87fskei4fa.fsf@localhost> <831qvy41oj.fsf@gnu.org> <87tu8rq2l6.fsf@localhost> <83czffzo73.fsf@gnu.org> <87a6aiqnpc.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="610"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ () (2022-05-21) Cc: Eli Zaretskii , theophilusx@gmail.com, acm@muc.de, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 23:30:30 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0VAE-000AZR-0o for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 23:30:30 +0200 Original-Received: from localhost ([::1]:58296 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0VAC-0004rq-UZ for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 17:30:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39454) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0V8D-0001TO-Hk for emacs-devel@gnu.org; Sun, 12 Jun 2022 17:28:25 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:60097) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0V8B-0005cK-Lp; Sun, 12 Jun 2022 17:28:25 -0400 Original-Received: from localhost ([::ffff:102.84.37.119]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000087C65.0000000062A65A75.000001B4; Sun, 12 Jun 2022 14:28:20 -0700 Mail-Followup-To: Ihor Radchenko , Eli Zaretskii , theophilusx@gmail.com, acm@muc.de, emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <87a6aiqnpc.fsf@localhost> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291105 Archived-At: * Ihor Radchenko [2022-06-12 20:52]: > I was referring to the markdown-mode and > Auctex to illustrate the _need_ to have numerous key bindings in order > to edit complex Org documents. It is not just something introduced into > Org out of the blue. Other people solved similar problems and did not > come up with significantly less key bindings. There are many markups and using various of them is very beneficial due to various outputs and qualities. Example is Asciidoc and Asciidoctor implementation AsciiDoc Writer’s Guide | Asciidoctor https://asciidoctor.org/docs/asciidoc-writers-guide/# and if I may say, there may be reasons why is Asciidoctor so much financially supported: Asciidoctor - Open Collective https://opencollective.com/asciidoctor or txt2tags: txt2tags https://txt2tags.org/ and many others like reStructuredText and Wiki and what else, too many. The way to go to minimize at least some key bindings is to find the union on what is common to each of those markups. Common markup tags are headers, italic, bold, underlined, monospaced, lists, links, tables, separators, etc. etc. Once it is found what is common, then Emacs and markup modes may define how those markups look like. Then we can use functions similar to facemenu-set-bold to get that bold markup in a way how a markup mode specifies it. Then if key binding is for example "C-c b" for "bold" that bold would appear different in HTML mode, rather like word but in Markdown it would appear as **strong** and in Org as *strong* and so on. Markup mode would define how those common markups are to be applied, while Emacs could have its standardized key bindings. That would make life easier for us who use multiple markups. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/