From: indieterminacy@libre.brussels
To: "Rodrigo Morales" <moralesrodrigo1100@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Virtually prefix headlines according to content
Date: Tue, 29 Jun 2021 13:26:00 +0000 [thread overview]
Message-ID: <2aaed4a5edef98e7d993f40eb39a0cd2@libre.brussels> (raw)
In-Reply-To: <87v95wq5e9.fsf@gmail.com>
Hi Rodrigo,
regarding syntax, it would be cool if you aligned the style to match Emacs' Hyperboles GitHub style:
=> https://github.com/rswgnu/hyperbole/blob/master/DEMO
```
** Github (Remote) References
For software developers who use Github for publishing and version control,
Github links are similar to social media links but reference specific Github
web pages.
Press the Action Key on github@rswgnu to go to RSW's gihub home page.
gh@rswgnu works too.
References to project home pages look like this (the / is required):
github#/hyperbole (uses user default setting)
github#/rswgnu/hyperbole
References to specific commits use the # hash symbol and short versions
of the git commit hash code:
gh#rswgnu/hyperbole/5ae3550 (if include user, must include project)
github#hyperbole/5ae3550 (project can be given with user default)
gh#5ae3550 (user and project defaults are used)
An Action Key press on the first commit reference above works because
user, project and commit hash code are all included. The second and
third versions require the setup of default values, as explained in
the commentary near the top of "hib-social.el".
Similarly, the same file above explains how to link to pull requests,
issues, branches and tags.
```
FYI, Hyperbole has been making improvements with regards to utility with Orgmode.
It may be worth you looking into how that functionality is implemented.
Kind regards,
Jonathan McHugh
June 29, 2021 1:27 PM, "Rodrigo Morales" <moralesrodrigo1100@gmail.com> wrote:
> * The context
>
> When taking notes in Org Mode, I usually store Github links of the
> repositories that are relevant to the topic I'm taking notes as
> headlines. For this reason, I've multiple headlines of the form within
> my notes (from my notes on Graph Theory):
>
> #+BEGIN_SRC org
> * cytoscape/cytoscape.js: Library for visualisation and analysis
> :PROPERTIES:
> :GITHUB: cytoscape/cytoscape.js
> :END:
>
> * simongray/clojure-graph-resources: List of Clojure resources
> :PROPERTIES:
> :GITHUB: simongray/clojure-graph-resources
> :END:
>
> * DONE What is an undirected graph? ...
> * DONE What is a directed graph? ...
> #+END_SRC
>
> * The question
>
> What I would like to know is whether it is possible to format a headline
> by taking into consideration the properties it has. For example, in this
> specific scenario, I would like to make all headlines that have a
> "GITHUB" to show "GH" before the actual headline (the content would look
> like this).
>
> #+BEGIN_SRC org
> * GH cytoscape/cytoscape.js: Library for visualisation and analysis ...
> * GH simongray/clojure-graph-resources: List of Clojure resources ...
> * TODO What is an undirected graph? ...
> * TODO What is a directed graph? ...
> #+END_SRC
>
> The reason why I'm asking this is because thus when collapsing
> headlines, I would know that an specific headline is a Github
> repository. In general terms, to ease the readibility of my Org Mode
> file.
>
> * Additional context
>
> A similar behavior is provided by org-num-mode (built-in function), so I
> guess that some way to accomplish this would be to look at the
> implementation of that mode and try to understand how that is
> accomplished.
>
> Any help is appreciated,
> Rodrigo Morales.
next prev parent reply other threads:[~2021-06-29 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 11:25 Virtually prefix headlines according to content Rodrigo Morales
2021-06-29 12:52 ` Eric S Fraga
2021-06-29 13:26 ` indieterminacy [this message]
2021-06-29 13:34 ` Juan Manuel Macías
2021-06-29 13:53 ` John Kitchin
2021-06-29 20:44 ` Samuel Wales
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=2aaed4a5edef98e7d993f40eb39a0cd2@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=emacs-orgmode@gnu.org \
--cc=moralesrodrigo1100@gmail.com \
/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).