Sébastien Gendre writes:
> Hello,
>
> I don't know if it's the correct place to ask it. If not, sorry to ask in
> the wrong place.
>
> How do you manage complex project with Org-mode ?
>
> I used Org-mode for several periods of time in recent years. It worked
> very well for short and day to day
On Mon, 28 Feb 2022 20:43:47 -0500 Sébastien Gendre wrote
> And I don't know how to manage this kind of projects with Org-mode. How
> to do it, without failing a 6 days project because I spent to much time
> on something else and I have only 3 days left with 3 half-day important
Hello,
I don't know if it's the correct place to ask it. If not, sorry to ask in
the wrong place.
How do you manage complex project with Org-mode ?
I used Org-mode for several periods of time in recent years. It worked
very well for short and day to day tasks. When only a few of theme have
i have a problem similar to this from a few months ago. in this case,
it seems to be when trying to pass a column with a quoted-string inside
of it. (this is on the "bugfix" branch.) my e-lisp code seems to get
just the initial part of the string from the cell with "odd" contents.
#+name:
Thank you very much for that suggestion.
Unfortunately, that does not seem to work for org-export-taskjuggler.
An exported taskjuggler file has extremely simple syntax. For a report, for
example, there is the header, "textreport id name {"
then a series of "attribute_name", "value" pairs such as
Hi Greg and Nicolas,
Greg Minshall writes:
> Nicolas and Juan Manuel,
>
> thanks very much. the bugfix branch seems to work for my case.
Thank you very much Nicolas. In my case it also works fine.
Best regards,
Juan Manuel
On Mon, Feb 28, 2022 at 3:34 PM Kaushal Modi wrote:
>
> On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
> >
> > Hej,
> >
> > I have noticed that properties that stretch over multiple lines using
> > the :value+: syntax are ignored by org-element-property and therefore
> > also by e.g.
On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
>
> Hej,
>
> I have noticed that properties that stretch over multiple lines using
> the :value+: syntax are ignored by org-element-property and therefore
> also by e.g. org-export-get-node-property when exporting to ics via
> ox-icalendar.el
I would really like the ability to use the ":myProperty+: " to create
multi-line properties for the org-export-taskjuggler exporter.
However, the mentioned patch is quite large and mostly focused on headline
caching, as far as I can tell.
@Ihor or @Hanno, Is there a patch just to get the
Nicolas and Juan Manuel,
thanks very much. the bugfix branch seems to work for my case.
cheers, Greg
On 2/28/2022 00:41, Richard Stallman wrote:
[[[ To any NSA and FBI agents reading my email: please consider > ]]] [[[ whether defending the US Constitution against all enemies, >
]]] [[[ foreign or domestic, requires you to follow Snowden's > example.
]]] > > The FSF accepts credit card
Hello,
Juan Manuel Macías writes:
> Greg Minshall writes:
> In any case, I don't know if that behavior should be considered a bug. I
> say this because other constructions with an unbalanced element,
> although org does not fontify them well, they are exported correctly:
>
> this is a
* ox.el (org-export-to-file): `write-region' instead of `write-file'.
* ox-odt.el (org-odt-template, org-odt--export-wrap): `write-region'
instead of `save-buffer'.
`write-file' and `save-buffer' trigger major mode changes, which leads
to various mode-related hooks being run. This is
On 2022-02-27 18:17 Bastien Guerry wrote:
> My gut feeling is that we should focus on making the mailing list more
> accessible for beginners, more useful for everyone before considering
> setting up another communication channel.
I totally agree with that.
Great, will do :) I realized at the last minute that some
`save-buffer' calls in `ox-odt.el' also need to be amended separately
(I was mostly testing these tweaks with HTML export, as it's faster /
simpler). If it's problematic, we can have that discussion over the
patch once I've submitted it.
Hi All,
I'm trying out the pre-release this week, and in thus doing, I met a
particularly strange issue related to Org Agenda's `mode-name'. And one
space in particular, the one that is added before
`org-agenda-current-span'. The `mode-name' for the Agenda is set by
Hello,
David Lukeš writes:
> Thanks, that's indeed a much better way of doing it :) One can even
> avoid the temp buffer altogether and write the `output' string
> directly with `(write-region output nil file)`.
Yup, even better.
> Shall I prepare a patch? Or would you rather do it yourself,
> What about using `write-region' instead of `write-file' and not touching
> `set-auto-mode' function?
Thanks, that's indeed a much better way of doing it :) One can even
avoid the temp buffer altogether and write the `output' string
directly with `(write-region output nil file)`.
Shall I
18 matches
Mail list logo
