emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix
Date: Tue, 05 Mar 2024 12:52:34 +0000	[thread overview]
Message-ID: <87le6w4z8t.fsf@localhost> (raw)
In-Reply-To: <87edczr4e1.fsf@bzg.fr>

Bastien <bzg@gnu.org> writes:

> Adding [BLOG] or [TIP] in the subject prefix allows for such messages
> to be referenced on https://tracker.orgmode.org/news (along with [ANN]
> messages). 
>
> It will then be possible to include these posts in the orgmode.org
> homepage, using e.g. https://tracker.orgmode.org/news.rss.
>
> This is experimental, let's see if this helps spread the word about
> useful blogs.

I am looking at https://tracker.orgmode.org/news and I feel that mixing
blog/tip entries with important announcements may not be very good idea.
May we put the blogs into a separate tab, leaving announcements stand
out?

Also, I do not see
https://list.orgmode.org/877cihmr45.fsf@posteo.net/T/#u listed.
May it be because in "[tip] Export to PDF with latexmk 'continuous
preview' option", "tip" is lowercase?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2024-03-05 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  8:55 [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix Bastien
2024-02-26 10:32 ` Juan Manuel Macías
2024-02-26 11:03   ` Ihor Radchenko
2024-02-26 13:00     ` Bastien Guerry
2024-02-26 12:58   ` Bastien Guerry
2024-02-27  8:54     ` jman
2024-03-05 12:52 ` Ihor Radchenko [this message]
2024-03-05 13:24   ` Bastien Guerry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le6w4z8t.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).