Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…)
Hi Richard, Richard Lawrence writes: > What about just adding a tag (:evening:, :morning:, etc.) to represent a > fuzzy time, with a plain date stamp, like <2018-12-04>? > > That would allow you to easily create a custom agenda view containing > just entries with fuzzy times (if they have a timestamp with just a > date, you can even filter for those that are coming up in the next > couple of days). Then when it's convenient, you can look at this agenda > view and schedule things that are still fuzzy more precisely. This sounds like a good idea, thanks! Especially combined with Ken Mankoff's, so that the event still is shown in the overall agenda at an approximately correct hour so I don't schedule two things at the same (fuzzy) time :) With your two ideas it should make a quite good workaround, thank you! Cheers, Leo
[O] CSV batch agenda
Hi all, I'm playing around with `org-batch-agenda-csv'. My question is, what is "String with extra planning info"? A quick experiment shows that it is what is displayed in the "normal" agenda right after the category. Also, what is "numerical priority" and how is it computed? I could find any reference in the manual. Again, a quick experiment suggests a number between 1000 and 2000, converging to 2000 as the item gets more and more overdue. Do I guess it right? TIA, -- Marcin Borkowski http://mbork.pl
Re: [O] ODT export --> opening in Okular?
On 2018-12-09 at 17:45 -0800, James Harkins wrote: > Anyway, the solution for now, as I'm under some time pressure, is to > declare that ODT export is broken on my system until I can scrape > together some time to upgrade org. PDF export is actually OK for now > (and working fine). But export is not the same as opening. Export should work. -k.
Re: [O] ODT export --> opening in Okular?
On Mon, 10 Dec 2018 07:25:13 +0800 briangpowell
wrote
> * Suggest you try changing this:
>
> ("\\.odt\\'" . "libreoffice6.0 %s"
> * To this instead:
>
> ("\\.odt\\'" . "libreoffice %s"
> --since "libreoffice6.0" is a specific link that is subject to change--not
> only by you but by your chosen operating system package manager
Nope.
$ libreoffice --help
The program 'libreoffice' is currently not installed.
(I installed libreoffice by downloading from their website, not using Ubuntu
packages -- because I had some issues with it a while back and the advice from
their user community is always, don't use system-bundled packages because they
are out of date.)
In any case, it doesn't make a difference: org still insists on issuing the
command for okular.
I also tried the full path to the binary /usr/bin/libreoffice6.0 -- still
exports to Okular.
As a final test, I deleted both the PDF and ODT entries from org-file-apps --
so that there is absolutely no reference in any org code file or variable to
okular -- and it is *still* opening the exported ODT in okular! Which strikes
me as insane.
org-open-file seems to be a rather complex function. I can't make heads or
tails of it. If I had to guess, I would suppose that it has some fallback
position that doesn't depend on org configuration variables.
Anyway, the solution for now, as I'm under some time pressure, is to declare
that ODT export is broken on my system until I can scrape together some time to
upgrade org. PDF export is actually OK for now (and working fine).
hjh
Re: [O] [PATCH] Bug: Org capture: Invalid use of ‘\’ in replacement text [9.1.14 (9.1.14-1049-g04641c-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20181203/)]
Hello, Allen Li writes: > Attached patch fixing this. > > This was caused by a bug in a feature that I did not realize existed > (prefixing each line in %i). I have also included patches to clarify > the documentation. I applied the documentation patch. Thank you. Regards, -- Nicolas Goaziou
Re: [O] ODT export --> opening in Okular?
* Suggest you try changing this:
("\\.odt\\'" . "libreoffice6.0 %s"
* To this instead:
("\\.odt\\'" . "libreoffice %s"
--since "libreoffice6.0" is a specific link that is subject to change--not
only by you but by your chosen operating system package manager
Unless of course, you intentionally run several versions of libreoffice,
which is possible but seems pointless
On Sun, Dec 9, 2018 at 6:07 PM James Harkins wrote:
> Hi,
>
> I realize I'm running an older version of org-mode (8.3.3), but things are
> working for me generally and I'm not in a position to monkey around with my
> environment right now.
>
> Anyway, something strange. A few months ago, I was able to export to ODT
> and the file would open in LibreOffice. But, just now, emacs insists on
> issuing a command to open it in okular.
>
> Creating ODT file...
> Running zip -mX0 project-notes.odt mimetype
> Running zip -rmTq project-notes.odt .
> Created /blah/blah/project-notes.odt
> Parsing archive file...done.
> Running okular /blah/blah/project-notes.odt --icon okular -caption
> Okular...done
>
> Okular? That makes no sense at all.
>
> I tried adding an entry to org-file-apps to force it to use libreoffice6.0
> to open ODT files, but this is having no effect.
>
> '(org-file-apps
>(quote
> ((auto-mode . emacs)
> ("\\.mm\\'" . default)
> ("\\.x?html?\\'" . "/usr/bin/firefox %s")
> ("\\.pdf\\'" . "/usr/bin/okular %s")
> ("\\.odt\\'" . "libreoffice6.0 %s"
>
> I can find no hard coded reference to Okular anywhere in the org source
> code.
>
> This is quite mysterious to me. If it's using a particular app to open
> this type of file, I should be able to find some settings or some
> instruction somewhere. But I can't.
>
> How to fix this?
>
> hjh
>
>
>
[O] ODT export --> opening in Okular?
Hi,
I realize I'm running an older version of org-mode (8.3.3), but things are
working for me generally and I'm not in a position to monkey around with my
environment right now.
Anyway, something strange. A few months ago, I was able to export to ODT and
the file would open in LibreOffice. But, just now, emacs insists on issuing a
command to open it in okular.
Creating ODT file...
Running zip -mX0 project-notes.odt mimetype
Running zip -rmTq project-notes.odt .
Created /blah/blah/project-notes.odt
Parsing archive file...done.
Running okular /blah/blah/project-notes.odt --icon okular -caption Okular...done
Okular? That makes no sense at all.
I tried adding an entry to org-file-apps to force it to use libreoffice6.0 to
open ODT files, but this is having no effect.
'(org-file-apps
(quote
((auto-mode . emacs)
("\\.mm\\'" . default)
("\\.x?html?\\'" . "/usr/bin/firefox %s")
("\\.pdf\\'" . "/usr/bin/okular %s")
("\\.odt\\'" . "libreoffice6.0 %s"
I can find no hard coded reference to Okular anywhere in the org source code.
This is quite mysterious to me. If it's using a particular app to open this
type of file, I should be able to find some settings or some instruction
somewhere. But I can't.
How to fix this?
hjh
Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…)
Hi Leo, Leo Gaspard writes: > In the process of migrating all my self-organization to org-mode, I > noticed there is something that cannot currently be encoded in > timestamps: fuzzy times, where an appointment is made for “Dec 4, Tue, > evening” but with the hours not yet fixed. > ... > To be perfectly honest, my ulterior motive here is to auto-generate > tasks “Decide of an exact time for [task]” a few days before the > timestamp. However, I haven't investigated yet whether that'd actually > be doable and I'm still pretty new to the lisp/emacs/org-mode > ecosystems, so this may be completely impossible. > > What do you think about this idea? Is there a better way to do what I'm > trying to do with current tools? What about just adding a tag (:evening:, :morning:, etc.) to represent a fuzzy time, with a plain date stamp, like <2018-12-04>? That would allow you to easily create a custom agenda view containing just entries with fuzzy times (if they have a timestamp with just a date, you can even filter for those that are coming up in the next couple of days). Then when it's convenient, you can look at this agenda view and schedule things that are still fuzzy more precisely. Hope that helps! -- Best, Richard
Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…)
Ken Mankoff writes: > On 2018-12-08 at 09:47 -0800, Leo Gaspard wrote: >> However, I think it may be a good idea to allow eg. this kind of >> timestamps: >> <2018-02-04 Tue evening> That would be handled as though it >> was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable), so >> that it would be both semantically correct (the time is still fuzzy) >> and correctly displayed (eg. on an agenda) >> [...] >> What do you think about this idea? Is there a better way to do what >> I'm trying to do with current tools? > > > I think this would be a neat feature. But as a first pass which can work > immediately, what about using one of the multiple text expansion packages > that are Org-agnostic to achieve this: Yasnippets or abbrev mode, for example? > > This doesn't maintain the "semantics (time still fuzzy)", but does let you > define and enter time ranges in a simpler way. Hmm… I guess some abbreviation or command could add the fuzzy time and add a comment to indicate that the time is fuzzy should work as a temporary workaround indeed, thank you for the idea :)
