Re: [O] org-info.js (un)maintained ?
Hello, Olivier Berger writes: > Looking at https://github.com/SebastianRose/org-info-js the code seems > rather unmaintained. > > On the other hand, there's a copy inside worg/code that seems a bit more > recent. Thank you for looking into this. > I haven't tried yet to contact Sebastian Rose and thought that maybe > others could enlighten me on the code's status before I dig more into > the issue. Even though you made a pull request on the repository, I think our best bet still is to contact Sebastian Rose for the time being. Regards, -- Nicolas Goaziou
Re: [O] why prepend "file://" to abs paths in html output?
Hello, Matt Price writes: > in org-html-link local links of the form > > "/some/path/to/file" > > are rewritten as > > "file:///some/path/to/file". > > This makes it difficult to write root-relative URL's in the way that one > might expect to be able to (so that export produces links like > > > > Is this really the most desirable behaviour? In html export, at least, I > would think most users would want to allow links of the kind I described. > But this seems like a conscious design decision; cf. these lines from > org-html-link: > > ;; If file path is absolute, prepend it with protocol > ;; component - "file://". > (cond > ((file-name-absolute-p raw-path) > (setq raw-path (org-export-file-uri raw-path))) > ((and home use-abs-url) > (setq raw-path (concat (file-name-as-directory home) raw-path > > I'm wondering whether a user oculd at least set a defcustom to control this > behaviour. Let me ask this the other way: is there any situation where "file://" prefix is desirable? Regards, -- Nicolas Goaziou
Re: [O] why prepend "file://" to abs paths in html output?
On Sat, Jul 8, 2017, 6:35 AM Nicolas Goaziou wrote: > Let me ask this the other way: is there any situation where "file://" > prefix is desirable? > I don't see why "file://" would be useful in html exports (or pdf, md, etc). It is probably needed only in org to org exports. > -- Kaushal Modi
Re: [O] why prepend "file://" to abs paths in html output?
Hello, Kaushal Modi writes: > I don't see why "file://" would be useful in html exports OK. Il remove the file:// scheme specifications then. > (or pdf, md, etc). Well, those are not related to network based protocols. Does it really make a difference in those cases? Regards, -- Nicolas Goaziou
Re: [O] why prepend "file://" to abs paths in html output?
I think it can be useful to write file: in the org-mode file, to make a clear distinction from internal links. But once it is clear that something is a link to a file, I guess you are right that it might not be needed in HTML. We will see what breaks. Carsten On Sat, Jul 8, 2017 at 4:08 PM, Nicolas Goaziou wrote: > Hello, > > Kaushal Modi writes: > > > I don't see why "file://" would be useful in html exports > > OK. Il remove the file:// scheme specifications then. > > > (or pdf, md, etc). > > Well, those are not related to network based protocols. Does it really > make a difference in those cases? > > Regards, > > -- > Nicolas Goaziou > >
[O] 911 and Call Centers was employment stats that don't change (fwd)
Is org-mode or a special-purpose contribution being used to handle 911 response centers and call center activities? If not, is org-mode even feasible for this kind of work? -- -- Forwarded message -- Date: Sat, 8 Jul 2017 09:50:47 From: Lisa Belville Reply-To: Blind exchange and discussion To: blin...@listserv.icors.org Subject: 911 and Call Centers was employment stats that don't change Here's some discussion about working as a 911 dispatcher and/or general call center reps from a blindness-oriented web site.Notice how critical the access to real time information is. https://www.zonebbs.com/boards.php?t=30408 Lisa Lisa Belville missktlab1...@frontier.com I'm great at multi-tasking. I can waste time, be unproductive, and procrastinate all at once.
Re: [O] 911 and Call Centers was employment stats that don't change (fwd)
Jude DaShiell writes: > Is org-mode or a special-purpose contribution being used to handle 911 > response centers and call center activities? > If not, is org-mode even feasible for this kind of work? That sounds like a pretty bad idea -- it's not the kind of work Org was made for, and more importantly that's an area where you'd need some hard requirements for reliability and security. Not very compatible with Org's more... flexible approach! > -- Forwarded message -- > Date: Sat, 8 Jul 2017 09:50:47 > From: Lisa Belville > Reply-To: Blind exchange and discussion > To: blin...@listserv.icors.org > Subject: 911 and Call Centers was employment stats that don't change > > Here's some discussion about working as a 911 dispatcher and/or > general call center reps from a blindness-oriented web site.Notice > how critical the access to real time information is. > > https://www.zonebbs.com/boards.php?t=30408 > > Lisa > > Lisa Belville > missktlab1...@frontier.com > I'm great at multi-tasking. I can waste time, be unproductive, and > procrastinate all at once.
[O] Documentation problem?
Aloha all, At 14.6, the manual says: The "Library of Babel" is a collection of code blocks. Like a function library, these code blocks can be called from other Org files. This collection is in a repository file in Org mode format in the `doc' directory of Org mode installation. The last sentence seems vague to me, and based on my likely partial understanding of some of the terms, it seems contradictory, too. What is meant by a "repository file"? Does "repository" express something about the file's location in the Org mode ecosystem, or does it refer to the contents of the file, which serves as a repository for source code blocks? When I read "Org mode installation" I think about the Org mode files installed on my computer. Yet, the org-plus-contrib package from ELPA lacks both a `doc' directory and library-of-babel.org. Perhaps I'm mis-interpreting something, but this last sentence seems demonstrably false to me. Is this: 1) user error? 2) a documentation problem? 3) a problem with the ELPA org-plus-contrib installation? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] why prepend "file://" to abs paths in html output?
Hello, Carsten Dominik writes: > I think it can be useful to write file: in the org-mode file, to make a > clear distinction from internal links. But once it is clear that something > is a link to a file, I guess you are right that it might not be needed in > HTML. We will see what breaks. Thinking about it, we should probably not remove the "file://" prefix. I cannot think of any situation where [[/absolute/path/to/file]] would match something like "", because "/" never matches web root directory. IOW, to re-use the OP's example, [[/static/images/unicorn.jpg]] is never a valid Org link, in the sense that it points to a non-existing file. Since the OP is writing a link only valid during HTML export, he might as well write raw HTML. Note that that "file:///static/images/unicorn.jpg" is not useful either, but at least it is logical. The only situation where we might do something is during publishing, when we know what web root directory – i.e., base directory – is. In that case, we could replace absolute file names starting with web root dir as root-relative URL. WDYT? Regards, -- Nicolas Goaziou
[O] Easy Templates
I am fairly new to orgmode and I have just begun trying to use source code blocks. I have a simple question that is not made clear in the Orgmode Manual. The manual states that to insert an Easy Template for a source code block, use: `<<>' `' `' and then `<' `l' `' to label it for LaTeX. But I cannot find anywhere in the manual where the `<<>' is explained. The section on typographical conventions says nothing about this. Can someone tell exactly what to type to insert a template for, say, LaTeX or emacs-lisp? Thanks, Bill
Re: [O] Easy Templates
Hi! > I am fairly new to orgmode and I have just begun trying to use source > code blocks. I have a simple question that is not made clear in the > Orgmode Manual. > > The manual states that to insert an Easy Template for a source code > block, use: > > > `<<>' `' `' > > > and then > > > `<' `l' `' > > > to label it for LaTeX. But I cannot find anywhere in the manual where > the `<<>' is explained. The section on typographical conventions says > nothing about this. IMHO you found an inconsistency in the documentation. `<<>' looks like a weird doubled quoting to me. > Can someone tell exactly what to type to insert a template for, say, > LaTeX or emacs-lisp? To get a source block template for emacs-lisp easily you could type the three keys `<' `s' `' and then type literally "emacs-lisp". HTH, Marco
Re: [O] Easy Templates
Marco, Thanks very much! Now it is clear to me. I didn't see or understand that the `<<>' was a literal `<'. So that actually makes sense to me now. Bill On 07/08/2017 05:14 PM, Marco Wahl wrote: Hi! I am fairly new to orgmode and I have just begun trying to use source code blocks. I have a simple question that is not made clear in the Orgmode Manual. The manual states that to insert an Easy Template for a source code block, use: `<<>' `' `' and then `<' `l' `' to label it for LaTeX. But I cannot find anywhere in the manual where the `<<>' is explained. The section on typographical conventions says nothing about this. IMHO you found an inconsistency in the documentation. `<<>' looks like a weird doubled quoting to me. Can someone tell exactly what to type to insert a template for, say, LaTeX or emacs-lisp? To get a source block template for emacs-lisp easily you could type the three keys `<' `s' `' and then type literally "emacs-lisp". HTH, Marco
Re: [O] why prepend "file://" to abs paths in html output?
Ni Nicolas, I think I agree. If I export org files as HTML for use on my local system, I probably want 'real' links and file:/// is probably the right thing as I don't want to have to also install the files in a local web server. However, when I want to export files to HTML and have them served by a web server, file:/// is not the right thing. Perhaps we need a way to easily set a context for web exports. If the context is set, then use it, otherwise, use file:/// (actually, I thought this was already there, but it has been a while since I did html exports where links were necessary). Tim Nicolas Goaziou writes: > Hello, > > Carsten Dominik writes: > >> I think it can be useful to write file: in the org-mode file, to make a >> clear distinction from internal links. But once it is clear that something >> is a link to a file, I guess you are right that it might not be needed in >> HTML. We will see what breaks. > > Thinking about it, we should probably not remove the "file://" prefix. > > I cannot think of any situation where [[/absolute/path/to/file]] would > match something like "", because "/" > never matches web root directory. > > IOW, to re-use the OP's example, [[/static/images/unicorn.jpg]] is never > a valid Org link, in the sense that it points to a non-existing file. > Since the OP is writing a link only valid during HTML export, he might > as well write raw HTML. > > Note that that "file:///static/images/unicorn.jpg" is not useful either, > but at least it is logical. > > The only situation where we might do something is during publishing, > when we know what web root directory – i.e., base directory – is. In > that case, we could replace absolute file names starting with web root > dir as root-relative URL. > > WDYT? > > Regards, -- Tim Cross
Re: [O] 911 and Call Centers was employment stats that don't change (fwd)
I doubt it would be feasible. Things like 911 call centres need real-time responsive apps which interface with different emergency services and where tasks are shared across a team and data is recorded in a consistent and standardised manner. They also need to be robust, fault tolerant and distributed with the ability to interface with many different comms channels. Bottom line, a highly complex system with demanding requirements that can be tested and are reproducible. Org is not strong in the collaboration area, does not interface well with other systems in real-time, is free form and unstructured and unlikely to handle the complex requirements of an emergency call centre. You will likely find there are only a handful of recognised apps which fulfil the requirements and they will be very specialised. Unfortunately, they are likely to also have very poor accessibility support. Tim Jude DaShiell writes: > Is org-mode or a special-purpose contribution being used to handle 911 > response centers and call center activities? > If not, is org-mode even feasible for this kind of work? -- Tim Cross
