From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Serving .org files for worg (was: Re: Library of babel help)
Date: Fri, 1 Jul 2022 12:42:18 +0700 [thread overview]
Message-ID: <t9m1fr$tsq$1@ciao.gmane.io> (raw)
In-Reply-To: <87wncxztzb.fsf@gmail.com>
On 01/07/2022 04:48, Tim Cross wrote:
>
> 1. Just using the .org as the suffix of the url instead of the .html did
> not work for me using two different browser. However, it did work for
> ihor, so either I did something wrong or there is something in my setup
> which is preventing that from working. Need to investigate further.
> However, that is not my main issue.
I do not think that a chance of such event is noticeable, but you may
observe different behavior because you tried to access different files.
More likely you get files saved to Downloads.
Tim, likely you can not work with browsers unless significant
customization is applied. Generally it is better to have virtual
machines with popular environments and as little modifications as
possible. Unfortunately just now I am preparing to move my VMs to
another disk, so I would prefer to postpone setting up another instance
suitable for such purpose.
> My main issue is that having to know you can change the suffix from
> .html to .org in order to get the source is insufficient. It won't be
> obvious to many users and will only make some sense to experienced org
> users. I think the link should be obvious and I think the server
> configuration should be set so that accessing the .org url gives a
> sensible result (i.e. prefer opening it as plain text to offering to
> download).
I do not mind to have explicit link to .org file. It may be placed to
the header section with table of contents and the donation link. Such
link may be like
https://git.sr.ht/~bzg/worg/tree/master/item/org-artwork.org (I have no
idea if it may add noticeable load to Drew DeVault's servers). However
SourceHut does not highlight org sources currently. On the other hand it
does not try to render them formatted, so sources are visible. Another
problem is long lines. Unfortunately they are not wrapped and the
following causes discrepancy with line numbers, so I can not suggest a fix:
/* main.min.112ca73b.css | https://git.sr.ht/static/main.min.112ca73b.css */
.code-view .highlight pre {
white-space: pre-wrap;
}
> The initial aim is to make the site consistent and the build process
> server independent. Ideally, anyone will be able to clone the repo, set
> a document root and run the build process to create a fully working
> local worg site. Little in this first stage is terribly contentious.
I am afraid, to run local instance of worg, it would be necessary to
explicitly specify MIME type for .org files otherwise they may be
attributed to Lotus.
next prev parent reply other threads:[~2022-07-01 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 8:15 Library of babel help Tim Cross
2022-06-16 9:30 ` Tim Cross
2022-06-30 7:23 ` Ihor Radchenko
2022-06-30 9:06 ` Tim Cross
2022-06-30 13:25 ` Ihor Radchenko
2022-06-30 15:45 ` Serving .org files for worg (was: Re: Library of babel help) Max Nikulin
2022-06-30 17:04 ` Max Nikulin
2022-06-30 21:48 ` Tim Cross
2022-07-01 5:42 ` Max Nikulin [this message]
2022-07-29 13:10 ` Max Nikulin
2022-07-30 3:29 ` Tim Cross
2022-09-28 5:59 ` Serving .org files for worg Bastien
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='t9m1fr$tsq$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).