Kaushal's Projects/Lobby

Discussion/help for any of my projects like ox-hugo, eless, my emacs config, tmux config, other dotfiles

Kaushal Modi

@kaushalmodi

and then various rabbit hole forks came down the way.. discovered webmentions and microformats, content security policy to make my site as ideally secure as possible, etc

Shreyas Ragavan

@shrysr

:D you still did a very cool job. I have not bothered with webmentions after my wordpress 'success'. Abandoned WP but the LAMP stack is useful. webmentions was another reason to move to your theme actually though. I think refined is very logically focused on the content. There are a few things I would like to add... (if I ever figure it out).

Kaushal Modi

@kaushalmodi

Sure thing, feel free to explore the theme.

You can reach out to me with questions. And of course as you find anything interesting to add to the theme, PR's are welcome

Shreyas Ragavan

@shrysr

Sure. I hope to contribute :) It would be very satisfying if I figure out how to :D lol.

I will keep you posted and dig deeper into your website config.

Kaushal Modi

@kaushalmodi

I might miss seeing the pings on Gitter, so you https://gitlab.com/kaushalmodi/hugo-theme-refined/-/issues is the best place for the theme's related queries

I will keep you posted and dig deeper into your website config.

Shreyas Ragavan

@shrysr

Right. I was wondering whether gitter / raise issues. Will raise an issue next time.

I guess that will help future users better as well.

Steven Penny

@muv1

What I want to do with Hugo, is to have pages and tags as you would normally
have. But in addition to that, I would like the option, of being able to have a
"Talk" page linked to any type of page. So if I have a normal page:

content/sunday/index.md

I would also like the option of making a Talk page:

content/sunday/talk/index.md

that can be accessed from the normal page. This is similar to Talk page on
Wikipedia, or Discussion page with Rosetta Code:

With normal pages, I find that I can do this:

content/sunday/_index.md

Then I am able to add Talk page no problem. However I might also want to add
Talk page to a Taxonomy, like this:

content/tags/talk/index.md

So I tried to implement that by creating:

content/tags/_index.md

but the Talk page is not recognized. Is this something that is possible?

Kaushal Modi

@kaushalmodi

index.md are leaf bundles

think of leaf bundles as leaf nodes in CS if you are from CS background (I think you are)

so the leaf bundles are the "end" nodes.. you cannot have anything more inside those

the _index.md on the other hand are branch bundles

you can have more branch and leaf bundles under _index.md

so content/sunday/_index.md is definitely the right way to go if you want to have a talk/index.md under content/sunday/

The "tags" is a special section

unless you actually have a tag literally named "talk", I think Hugo might not generate that

The best way forward is to create a minimal git repo that you can share on https://discourse.gohugo.io/

If you don't have an account there, I sincerely recommend create one ( you can have discourse accounts created using your GitHub identity)

Once you share your minimal example repo there, folks will help you reach what you exactly want to do

Kyle Fring

@k-f-

In ox-Hugo is it possible to have the possible scenario:

blog.org & extra-content.org where blog.org when exported links to just a single defined heading or subheading in extra-content.org?

And the processes that as a

post/page

Kaushal Modi

@kaushalmodi

@k-f- I didn't understand, do you want to export a page from extra-content.org as a post/foo-page and then link that from another page exported from blog.org?

it might be better if you first model the structure using plain .md files and share the tree structure of that

Kyle Fring

@k-f-

@kaushalmodi https://gist.github.com/k-f-/cd8b27c1ee3eee584e8c2a6b31f32075

Kaushal Modi

@kaushalmodi

ah yes, use #+include

I have in fact used that to prevent copy pasting huge chunks of text in ox hugo test Org file

Kyle Fring

@k-f-

Awesome. Thanks. Sorry if it was tricky to explain.

Kaushal Modi

@kaushalmodi

you will find many such examples in there: https://github.com/kaushalmodi/ox-hugo/blame/master/test/site/content-org/all-posts.org#L1014

Sorry if it was tricky to explain.

No worries, code is the best way to communicate :D

.. or a minimal example in this case

Kyle Fring

@k-f-

Perfect <3

Kaushal Modi

@kaushalmodi

You can find more info on that syntax on https://orgmode.org/manual/Include-Files.html

Kiran Shila

@kiranshila

w.r.t ox-hugo, are latex export blocks supposed to just work?

Kiran Shila

@kiranshila

I opened an issue for it here kaushalmodi/ox-hugo#381

Kaushal Modi

@kaushalmodi

are latex export blocks supposed to just work?

No, the ox-hugo exporter is supposed to ignore unrelated export blocks. I have added my comments on that issue.

Vindaar

@Vindaar

Hey @kaushalmodi! Just something you maybe know: when working with ntangle (but in general when working with code blocks in org) I'm often annoyed that reading the stack traces of the bugs I managed to include in my code, because I can't jump to the line in the source code (unless I open the tangled file in another buffer of course).
So I was wondering if there is a way to display line numbers for each code block in an org mode buffer? How do you deal with this?

Kaushal Modi

@kaushalmodi

@Vindaar I haven't come across the need to do that. But now that you say it, I can see how annoying it can get without the line numbers. Reach out on the org mode mailing list; it's very possible someone has figured this one out

Vindaar

@Vindaar

Ah, thanks. That's probably a good idea then. I'm using org-edit-src-block sometimes. However, things probably get complicated quickly when working with multiple blocks that tangle to a single file. Maybe someone has an idea there

Bruno Henriques

@bphenriques

Heya! :wave: Did anyone setup a CI tool to run (org-hugo-export-wim-to-md :all-subtrees nil nil nil) on all the .org files?

In my setup, my links are broken when I run the CI tool but if I export manually in Emacs (using the chord) the links become alright. My setup is with HUGO bundles but managed avoid defining HUGO_BUNDLE or FILE_EXPORT.

My brain is going haywire with this :sweat_smile:

CI snippet:

(dolist (org-file (directory-files-recursively org-folder "\.org$"))
    (with-current-buffer (find-file org-file)
      (message (format "[build] Exporting %s" org-file))
      (org-hugo-export-wim-to-md :all-subtrees nil nil nil))))

I can share the branch once I wrap it

Bruno Henriques

@bphenriques

The branch is this one in master: https://github.com/bphenriques/knowledge-base

If you run locally using make clean build-content serve and go to Uncategorized -> Lightbend Academy -> Reactive Principles Example - git you will find a link to Actor Model that should be broken when running locally.

Now.. I found an additional hint.. the link is not broken on the published web-site (see https://bphenriques.github.io/knowledge-base/docs/uncategorized/lightbend-academy/) so it is something broken between the CI emacs installation and my own DOOM emacs :thinking:

Bruno Henriques

@bphenriques

something broken between the CI emacs installation and my own DOOM emacs

:point_up: Solved this by changing the Makefile: HOME=/tmp/knowledge-base-build/ emacs (...) this allows running the CI script without conflicting with my emacs installation.

Kaushal Modi

@kaushalmodi

@bphenriques Hello! I signed into Gitter after a long time. I don't get emails for pings here so I didn't know that these messages existed. Feel free to open an issue on ox-hugo repo next time. Do you still have any questions regarding that?

Vindaar

@Vindaar

Hey @kaushalmodi! Are you around by any chance?

Where communities thrive

People

Repo info

Activity