From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Sacha Chua Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: SachaC-news Date: Tue, 21 Nov 2023 11:07:19 -0500 Message-ID: <874jhfjdjc.fsf@sachachua.com> References: <87o7fyix8e.wl-cnngimenez@disroot.org> <877cmereoa.wl-cnngimenez@disroot.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32057"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: rms@gnu.org, emacs-devel@gnu.org To: Christian Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 21 17:08:30 2023 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 1r5TIb-00085i-Ha for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Nov 2023 17:08:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r5THk-00036g-Oj; Tue, 21 Nov 2023 11:07:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r5THj-00036R-5i for emacs-devel@gnu.org; Tue, 21 Nov 2023 11:07:35 -0500 Original-Received: from mail-qk1-x72e.google.com ([2607:f8b0:4864:20::72e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1r5THf-0005O6-6O for emacs-devel@gnu.org; Tue, 21 Nov 2023 11:07:34 -0500 Original-Received: by mail-qk1-x72e.google.com with SMTP id af79cd13be357-778925998cbso367852785a.0 for ; Tue, 21 Nov 2023 08:07:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sachachua-com.20230601.gappssmtp.com; s=20230601; t=1700582849; x=1701187649; darn=gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=Zqo8/MxjtNBMeCOAOfpZpFwjfnU1eyEIV1R6yrAVXkQ=; b=o2mNZaSwoAk4Rzh8WfO5MmzERzJuag1TUuDbBw8/yvAPvS+l/XMt3C8MSt9Q3PRpoG xFF3gHUdlltdTx9gRYMRkq9a6l0Q28NYW3LsEQjOvwUofnMLKai9CDdtWfDumJ2Xr56u fVBvnqG1MG+GPF+vYf2nZnKILrKM8t0UaQAT00vuDbFCHC/2Ne1K7+dOKxVCsXtWrKF7 DQsd8tnofPZJ0g89RqiXEZ4MyHiuIxbnaRTDJ3VNeX0UfKCnFJ2epbS3jdPw666XGX/M 0dUGTTqVfJYytoq8nYz39qSVGBNs3N6t1sgqUfKImWbGwZYKh54wBnXGvcwkjHtVQPjS MoYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700582849; x=1701187649; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Zqo8/MxjtNBMeCOAOfpZpFwjfnU1eyEIV1R6yrAVXkQ=; b=l7UvnYz5B+m8tyxbMoKXqLvZgZjhIzjg5fhyjtb3FmqHRLKmE1YoahdlwJF44EjTay H/L5PH+9LEpzJPsdQe48KKKLFo0rBYswchiQMIJkU62j/ueZO0Ca+x/iNxyVsP1VtGGV 94YBKSKI8WChKBcpXK6Ln8dl43oNy+y/10MKv1WbAMNeyT6rGJNYwUG9jJSoj2DrET4+ ibTjNatUGS3+fVNeJg1/2weCEdWYdNtMyK+IRwuJD5gcow5k1KsS8UVsBY26/KFa6we/ lQT27YQB8TFIohmWfphBV0rbP5FMdCKpZLSGsi/rU39K09WdfH52kAqij4LMo+aGmQl8 rD5A== X-Gm-Message-State: AOJu0YyeupWsA23wLZbZAr0/ZwUwYx1wAp1d3DQkqBgjca2xoalfcFYq /UHi6b9Tn4e/kxnGf+XtSXG6Hh1fQV+olBpjYHc= X-Google-Smtp-Source: AGHT+IH1aGBwv95YDqKhtGn6oyOXz52KsvmE4yYWmDqSOod6DsDamuxWWT85+8w1TtXPm1FOlwulww== X-Received: by 2002:a05:620a:904:b0:77a:7763:8ab with SMTP id v4-20020a05620a090400b0077a776308abmr11656679qkv.54.1700582849594; Tue, 21 Nov 2023 08:07:29 -0800 (PST) Original-Received: from sacha-x220 ([76.69.148.251]) by smtp.googlemail.com with ESMTPSA id kr5-20020ac861c5000000b00421ae93b7a5sm3724383qtb.2.2023.11.21.08.07.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Nov 2023 08:07:28 -0800 (PST) In-Reply-To: <877cmereoa.wl-cnngimenez@disroot.org> (Christian's message of "Sat, 18 Nov 2023 17:26:29 -0300") Received-SPF: none client-ip=2607:f8b0:4864:20::72e; envelope-from=sacha@sachachua.com; helo=mail-qk1-x72e.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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313115 Archived-At: Christian writes: Hello, Christian, all! Christian: Neat idea, thanks for making it! =) >> What other formats does this repository store postings in? If it has >> -- or can generate -- plain text, that should be preferred. >> There are users who like Org fornat, but it is not Emacs's preferred >> way of showing information. > Sacha Chua creates her blog posts using this file written in > Org-mode. This mode is installed by default on Emacs 29 [1] and > can export to other formats: LaTeX, HTML, plain text, TeXInfo > and info (by installing ox-texinfo), etc. I could take another couple of minutes during the export process and export them as text and HTML as well. Here are both in my fork of your Sourcehut: https://git.sr.ht/~sachac/sachac-emacs-news . The Org version seems easier to parse, though. > Mmm... I suppose... I can add a customization to show an > exported buffer instead the Org-mode buffer. For example, if > sachac-news-show-plain-text is set to t, it will do the > overall process, but add an extra step to export the Org file > into plain text... or even generalize this idea to use any > export dispatch function... I believe it can be > implemented... what do you think? Yeah, it's probably better to do it on-the-fly, so people can get different versions of whatever they like. Making the backend selectable sounds like a possibly useful thing, in case maybe someone wants to use one of the Emacs News categories as a starting point for, say, their Markdown-based blog post... > Recently, I have just added a customization variable to set the > URL to Sacha's Emacs News repository (see [3]). By default, its > value is [4] which is a clone of the original. This repository > will be automatically updated once a day, if there is a new > blog post. However, you can change it to any other repository > URL with an index.org file if you like. Sure, we could use your repo (or my fork of your repo) if you like. Or if you add me as a collaborator on your repo, I can add it to the list of repos to push to... > I have an account on savannah.gnu.org. If it is needed, I can > request a new repository there. But it will require some time > to be approved. I wasn't sure if Emacs News is eligible for Savannah hosting, since I link to lots of YouTube videos and the occasional commercial workshop being advertised by people. (Goodness knows emacs-devel has seen lots of discussions about MELPA, even...) Happy to set up another repo there if people feel it's all right. Decentralized source control for the win! > Sacha Chua maintains her emacs-news blog posts [6], and creates them > by using the index.org file in that archive (or so it seems as far as > I can understand the code in it, I have not asked her yet!). Yup, that's pretty much it. >> Org format is NOT the Emacs standard or preferred format, and not >> everyone uses it. Therefore, if we add a command to display some >> useful information, it should not use Org format. >> The best format to use is plain text. > Maybe, the name "Org" is not correct? I mean Org-mode [7] (I call it > "Org" casually, sorry for that)... I thought it is considered as a > plain text format. I love it and use it for... well... almost > everything. If I am wrong in any way, please tell me. I use Org because that makes it easy to export to different formats with hyperlinks. I like the conciseness of working with the titles for the most part while easily being able to access the URLs as needed. I also like having custom package links that open up package descriptions on my computer and export to regular HTML or ASCII links when I'm publishing. It's easy to rearrange bulleted lists, too. If people open the Org files, they can mostly follow the hyperlinks without loading any custom configuration. I'm going to keep Org as my source data format instead of using something like Hyperbole and/or Markdown. If we want the source data available in different formats, I can add that to my publishing process and keep that in the repo. It takes me a few minutes to export the whole file, so it's not a big deal. I'm guessing when people want to see the data, they'll usually want to see hyperlinked titles instead of titles + URLs (as in the ASCII export) while still being able to access the URLs if needed. I think taking advantage of Org's existing functionality makes sense here. Of course, the package can display things in different formats for people who prefer those. For people's convenience, I post HTML/Org/TXT to the emacs-tangents mailing list, so the information is available there in multiple formats. Fetching the index.org without git could work if you grab the whole file using the raw URL, like https://git.sr.ht/~sachac/sachac-emacs-news/blob/master/index.org ? It's 3.8MB (sorry server operators). I keep everything in one file to make it easier to check for duplicates. Would it help if I wrote the last post as a separate file, as in https://git.sr.ht/~sachac/sachac-emacs-news/tree/master/item/most-recent.org (or .txt or .html)? Sacha