> Thorsten Jolitz writes:
> PS
> you do have this variable defined, right?
> ,
> | mail-header-separator is a variable defined in ‘sendmail.el’.
> | Its value is "--text follows this line--"
> |
> | Documentation:
> | Line used to separate
Hi Thomas,
"Thomas S. Dye" writes:
> Instead, let's move the project forward with the understanding that
> if it proves to be a bad idea, then the Org mode community will have
> Nicolas' very nice .texi file (with backports by Kyle Meyer) to fall
> back on.
Maybe we are
Hi Nicolas,
Nicolas Goaziou writes:
> I disagree. My motivation is not to attract more contributors. I don't
> think this was Thomas and Jonathan's motivation when they started the
> project either, but I may be wrong.
For the record, I think having more contributors
Hi Nicolas,
Nicolas Goaziou writes:
> You recently re-introduced a file named "orgmanual.org" in contrib/
> alongside "manual.org". The former is apparently outdated.
Yes, my mistake, fixed now.
--
Bastien
Hi Achim,
Achim Gratz writes:
> I've posted a working Makefile back when Thomas was working on the
> manual and it is still working with minimal modifications. If you
> decide you want to have this (and exactly which way) I'm sure that can
> be further refined in a matter of
Uwe Brauer writes:
"Thorsten" == Thorsten Jolitz writes:
>
>> Uwe Brauer writes:
>> "Thorsten" == Thorsten Jolitz writes:
>>>
>>> > Joseph Vidal-Rosset writes:
>>> > Hallo
>>>
phillip.l...@russet.org.uk (Phillip Lord) writes:
> Probably, by the time all of the manuals are in org-mode,
> machines will be significantly faster, there will be emacs-free org mode
> converter, or we will have hit the heat death of the universe. Perhaps
> it's not a problem.
:)
The output
>>> "Thorsten" == Thorsten Jolitz writes:
> Uwe Brauer writes:
> "Thorsten" == Thorsten Jolitz writes:
>>
>> > Joseph Vidal-Rosset writes:
>> > Hallo
>>
>> >> I know that the subject of my email exists
Aloha Bastien,
I disagree that the manual project should move into a one year
probation where success is measured by the number of contributors.
So, my response to LETS GO! is NOT THERE!
Instead, let's move the project forward with the understanding
that if it proves to be a bad idea, then
Eric S Fraga writes:
> On Tuesday, 6 Mar 2018 at 11:23, Robert Horn wrote:
>> I discovered that the lines ( the body of a headline):
>> *** real headline
>>* example
>>:SCHEDULED:
>>
>> cause agenda processing to fail. It tries to parse as a
>> timestamp. The parser used by
Uwe Brauer writes:
"Thorsten" == Thorsten Jolitz writes:
>
>> Joseph Vidal-Rosset writes:
>> Hallo
>
>>> I know that the subject of my email exists already.
>>>
>
Thorsten Jolitz writes:
> Uwe Brauer writes:
>
> "Thorsten" == Thorsten Jolitz writes:
>>
>>> Joseph Vidal-Rosset writes:
>>> Hallo
>>
>>>> I know that the subject of my email exists already.
Hi Nicolas,
Christian Moe writes:
>>> 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
>>> (setq
Uwe Brauer writes:
"Thorsten" == Thorsten Jolitz writes:
>
>> Joseph Vidal-Rosset writes:
>> Hallo
>
>>> I know that the subject of my email exists already.
>>>
>
Dear all,
Many thanks for your responses.
So as I understand it,there are two ways to achieve what I am trying to
do: either through diary, or through capture.
I am not sure which I should choose, though.
Since it seems my initial message was somehow unclear, let me try to
explain what I am
On 3/6/18, Achim Gratz wrote:
> I haven't looked at how often changes to Org's manual actually originate
> on the Emacs side in one development cycle of Emacs (which is generally
> a year or more, but it can't be that much.
it is an interesting technical question whether we
Hi Tim,
Tim Landscheidt writes:
>> - https://orgmode.org/org-remember.pdf
>> - https://orgmode.org/worg/code/org-info-js/
>> - https://orgmode.org/worg/org-contrib/babel/languages.html
>> - https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
>> -
Bastien Guerry writes:
>> Exactly. Emacs will anyways ship with org.texi. So moving the manual
>> source to Org in the Org repo shouldn't concern the Emacs repo.
>
> Yes, but it is still a concern for Emacs contributors like Glenn and
> others who occasionnally make corrections in Emacs' org.texi.
Shérab writes:
> Dear all,
[...]
> When I want to schedule a dinner with John, what I currently do is:
>
> 1. C-c a a
>
> 2. Look for a date
>
> 3. (say I find that April 1st isalright)
>
> 4. quit the agenda view
>
> 5. Visit the buffer corresponding to
I wrote:
> […]
> The following links in Emacs master's doc/misc/org.texi and
> lisp/org are broken (404):
> - https://orgmode.org/org-remember.pdf
> - https://orgmode.org/worg/code/org-info-js/
> - https://orgmode.org/worg/org-contrib/babel/languages.html
> -
Aloha Bastien,
Bastien writes:
Hi Thomas,
"Thomas S. Dye" writes:
Instead, let's move the project forward with the understanding
that
if it proves to be a bad idea, then the Org mode community will
have
Nicolas' very nice .texi file (with backports by Kyle Meyer) to
fall
On Tuesday, 6 Mar 2018 at 22:15, Shérab wrote:
[...]
> I am fine with steps 1 to 3 but would like to do steps 4 to 8 in a much
> more efficient way, without having to re-enter the date, but with the
> same result,i.e. the heading being added atthe endo of ~/gtd/agenda.org
>
> Do I make more
On Tuesday, 6 Mar 2018 at 11:23, Robert Horn wrote:
> I discovered that the lines ( the body of a headline):
> *** real headline
>* example
>:SCHEDULED:
>
> cause agenda processing to fail. It tries to parse as a
> timestamp. The parser used by agenda appears not to enforce
Hello Thomas,
as a preamble, let me say that I appreciate the directness of your
message and the civil tone of this conversation. I understand there
are frustrations lingering around, I have my own too, so let's keep
this thread as constructive as possible, because we all deserve it
as a
Hi Kaushal,
Kaushal Modi writes:
> Exactly. Emacs will anyways ship with org.texi. So moving the manual
> source to Org in the Org repo shouldn't concern the Emacs repo.
Yes, but it is still a concern for Emacs contributors like Glenn and
others who occasionnally make
Hello,
John Kitchin writes:
> I am pretty sure this isn't possible. The headers get overridden by the
> most local settings. There isn't a way to concatenate them. In some cases
> there isn't a way to figure out what you want, e.g. if a heading property
> said ":tangle
>>> "Thorsten" == Thorsten Jolitz writes:
> Joseph Vidal-Rosset writes:
> Hallo
>> I know that the subject of my email exists already.
>> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
> This works
Hello,
Luke writes:
> The face of the clocked time does not seem to change when the clock
> overruns (typically it changes to a red background).
>
> I'm no lisp expert, but after digging around in the code it looks like
> the problem is in
Hello,
how can I concatenate header args? Let's assume I have an Org structure
like follows:
* foo
:PROPERTIES:
:header-args: :flags -Wall
:END:
** bar
#+begin_src C :flags -lm
#+end_src
Now I want the code to be compiled with -Wall _and_ -lm.
Regards
hmw
Aloha Bastien,
Bastien Guerry writes:
Maybe this is where some misunderstanding arose: to me, there
was no
_project_ to migrate to manual.org -- it was an idea in the air
after
you made your experiment and we now have the decision at hand
because
the project is, well, DONE.
We could have
>>> "Thorsten" == Thorsten Jolitz writes:
> Joseph Vidal-Rosset writes:
> Hallo
>> I know that the subject of my email exists already.
>> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
> This works
I am pretty sure this isn't possible. The headers get overridden by the
most local settings. There isn't a way to concatenate them. In some cases
there isn't a way to figure out what you want, e.g. if a heading property
said ":tangle no" and your header said ":tangle yes" it would not make
sense
I discovered that the lines ( the body of a headline):
*** real headline
* example
:SCHEDULED:
cause agenda processing to fail. It tries to parse as a
timestamp. The parser used by agenda appears not to enforce the
requirement that headlines begin with asterisks on the left
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hello,
Daniel P Gomez writes:
> I noticed that (buffer-file-name (buffer-base-buffer)) will always
> return nil because `org-export--prepare-file-contents` is called in
> `org-export-include-keyword` after a call to `with-temp-buffer`. Two
> possible solutions to this
My 2¢ on this topic:
1. org is an excellent tool for writing. I cannot consider writing with
any other tool these days.
2. texi is an excellent tool for reading/browsing
documentation. Likewise, I cannot imagine doing so in another tool
(in the Emacs sphere).
We should find a way to
36 matches
Mail list logo