Is there a way to set properties using other properties? Doesn't matter
if its on export only, though it would be nice to have it in-situ.
here's an example (obviously doesn't work), where a project properties
for the project client only needs the CLIENT property filled, the rest
of it automatic
I agree. use `file::name` is better.
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Tue, Jan 23, 2018 at 3:24 AM, Ni
Kaushal Modi writes:
> Thank you. I'd like to see Org snippets in src blocks as they are not any
> "raw" monospace text blocks. But if no one else has a strong opinion for
> using src blocks for Org snippets, then I guess I'll have to concede.
There is another issue with "begin_src org" blocks.
Nicolas Goaziou writes:
> Fixed. Thank you. I also updated documentation and added tests.
As a side note, file:name syntax is a bit weak. It prevents using colons
in a name, as reported by the linter. I don't know if the feature is
used extensively but it may be worth considering changing refere
Bastien Guerry writes:
>> Why do we need it? If it is mandatory (I fail to see why, since we
>> provide the source of the info file), can we include it read-only?
>
> It is mandatory, as long as the GNU standard for documentation is to
> provide it as a .texi file.
It can always be generated for t
Hello,
John Kitchin writes:
> I don't recall how I learned about that, I guess maybe in some library of
> babel documentation somewhere. I confirmed it does work in 8.2.10, e.g.
> just with emacs -Q.
>
> There are a few changes in org 9 to org-babel-lob-execute-maybe
> and org-babel-lob-get-info
On Mon, Jan 22, 2018 at 12:20 PM Nicolas Goaziou
wrote:
>
> Again, Org manual, as published in "orgmode.org", is generated through
> Texinfo, which treats "begin_src org" exactly as "begin_example". So,
> switching to "begin_src org" will not give us Org fontification in HTML
> output.
>
Ah, OK.
Kaushal Modi writes:
> I am hoping that using "begin_src org" preserves the meta data that a code
> block is an Org snippet when the Org manual HTML pages are published on
> orgmode.org.
Again, Org manual, as published in "orgmode.org", is generated through
Texinfo, which treats "begin_src org"
Aloha Bastien,
Bastien Guerry writes:
Hi Nicolas,
"manual.org" was updated a month ago, and, so far, nobody
complained
about it. So, I think it's a good time to discuss about what
could be
done next.
Having the manual in .org is a great achievement, congrats to
anyone
who worked on this
On Mon, Jan 22, 2018 at 11:02 AM Nicolas Goaziou
wrote:
> "manual.org" is not meant to be exported to HTML through "ox-html", but
> using Texinfo itself. AFAIK, Texinfo does not highlight specially Org
> syntax, so using "begin_src org" is not very important for export.
>
I am hoping that using
Bastien Guerry writes:
> I've added (org-list-description-max-indent . 5)
OK.
> Me too, for the same argument. But this points to a strong limitation
> to `org-adapt-indentation' for which I'd like to propose this change.
>
>(setq org-adapt-indentation t) => current behavior
> (se
On Mon, Jan 22, 2018 at 11:35 AM Bastien Guerry wrote:
> what do you think of the proposal to have
>
> (setq org-adapt-indentation 'content)
>
> set :PROPERTIES: aligned with the beginning of the headline,
> while leaving content unindented?
>
> I'd also like to have the better of both worlds w
Kaushal Modi writes:
> - use example blocks for Org syntax instead of "begin_src org",
>
>
> I'd prefer "begin_src org". When these manuals are converted to HTML,
> we can use syntax highlighting to format comments, etc in Org
> snippets. I think it's good to retain the meta data that that
Hi Kaushal,
Kaushal Modi writes:
> I have always started PROPERTIES at col 0. With org-indent-mode
> enabled, it doesn't matter.. looks pretty (PROPERTY drawer in below
> screenshot actually starts at col 0):
what do you think of the proposal to have
(setq org-adapt-indentation 'content)
se
Christopher W Ryan writes:
> I'm a longtime LaTeX user and a more recent org mode user. So I've always
> had LaTeX installed on any computer on which I was using org mode. I'd like
> to introduce org mode to a co-worker unfamiliar with the whole concept of
> plain text files, markup, and literate
Hi Nicolas,
thanks for your answer.
Nicolas Goaziou writes:
>> fill-column: 70
>
> This is already the case.
Okay, I've found .dir-locals.el.
>> org-list-description-max-indent: 5
>> org-edit-src-content-indentation: ?
>
> It is 2. I'd favor 0, but I don't care much.
I've added (org-list-des
Hello,
Kaushal Modi writes:
> I'd prefer "begin_src org". When these manuals are converted to HTML, we
> can use syntax highlighting to format comments, etc in Org snippets. I
> think it's good to retain the meta data that that is not an arbitrary block
> of text, but Org data. Can you please re
Hi all,
>> Would they need to install LaTeX too, or is org mode self-contained and
>> able to export to pdf without LaTeX an friends installed?
>
>
> Yes, they'd need to have a LaTeX distribution installed on their system. In
> my experience, installing the full latest version of TexLive is the ea
Hello Christopher
I have a docker image with LaTeX installed in order not to "pollute" my
local filesystem with the 4GB of additional libraries a full LaTeX
installation requires.
If your co-worker is a software developer you could use that approach.
Here is mi Dockerfile for LaTeX:
FROM ubuntu:
On Mon, Jan 22, 2018 at 8:51 AM Nicolas Goaziou
wrote:
> > org-edit-src-content-indentation: ?
>
> It is 2. I'd favor 0, but I don't care much.
>
I also favor 0, less white space noise, the better.
> > This is necessary so that contributors don't mess up accidentally with
> > the desired forma
On Mon, Jan 22, 2018 at 8:56 AM Rasmus wrote:
>
> Could we use .dir-locals.el to ensure that the correct settings are
> loaded?
>
+1
As for their values, I have no strong preferences, but I’d prefer settings
> are either automatically loaded or that they are like the default settings
> so that
On Mon, Jan 22, 2018 at 9:57 AM Christopher W Ryan
wrote:
> Would they need to install LaTeX too, or is org mode self-contained and
> able to export to pdf without LaTeX an friends installed?
>
Yes, they'd need to have a LaTeX distribution installed on their system. In
my experience, installing
I'm a longtime LaTeX user and a more recent org mode user. So I've always
had LaTeX installed on any computer on which I was using org mode. I'd like
to introduce org mode to a co-worker unfamiliar with the whole concept of
plain text files, markup, and literate programming, etc. Would they need
t
Bastien Guerry writes:
> I'm all for editing manual.org instead of org.texi in the long run.
>
> Before moving manual.org into doc/, I'd suggest we agree on editing
> variables like `fill-column' and the like:
>
> fill-column: 70
> org-list-description-max-indent: 5
> org-edit-src-content-indenta
Hello,
Bastien Guerry writes:
> Before moving manual.org into doc/, I'd suggest we agree on editing
> variables like `fill-column' and the like:
>
> fill-column: 70
This is already the case.
> org-list-description-max-indent: 5
> org-edit-src-content-indentation: ?
It is 2. I'd favor 0, but I
Hi Nicolas,
> "manual.org" was updated a month ago, and, so far, nobody complained
> about it. So, I think it's a good time to discuss about what could be
> done next.
Having the manual in .org is a great achievement, congrats to anyone
who worked on this titanic task!
I'm all for editing manual
Because some MELPA package requires `org`. So Emacs will **force** install
`org` package from MELPA. But it is delay with source code Org.
I use source code org with use-package like this:
```
(use-package org
:load-path "~/Code/Emacs/org-mode/lisp/"
:pin manual
;; :mode (("\\.org$" . org-mod
27 matches
Mail list logo
