[O] HTML :exports both problem
Try this at home: #+begin_src lisp :results output :exports both (dotimes (i 4) (format t "~3d " i)) #+end_src #+RESULTS: : 0 1 2 3 #+name: #+begin_src lisp :exports both (defun multabl () (dotimes (x 20) (dotimes (y 20) (format t "~3d " (* (1+ x) (1+ y (format t "~%"))) #+end_src #+name: #+begin_src lisp :exports both (defun dt-test () (let ((y 0)) (dotimes (x 5 y) (format t "~3d " y #+end_src What I get when I export to HTML is bizarre, i.e., the results of the first code block don't appear, rather, the *name* of the last function! If I put the last two blocks between #+BEGIN_COMMENT and #+END_COMMENT, it behaves normally and shows the results. Am I missing something? LB
Re: [O] Getting feedback from a website created with OrgMode ??
John Hendy writes: > On Sun, Nov 18, 2018 at 4:54 PM David Masterson > wrote: >> >> I'd like some ideas on how to create a website with OrgMode. OrgMode is >> very good at creating static web-pages of any sort of structure. What I >> think I'd like to do is create a more dynamic web-page. My particular >> use-case is the following: >> >> 1. I'd like to create a website of information for my family of calendar >> information and financial information that they might need in day to day >> keeping track of family needs. >> >> 2. I'd like the family to be able to comment on the information as >> needed to let me know if something is wrong or missing. This might be a >> comment at the bottom of the web-page or an email feedback with a tag of >> the particular web-page (so I can find it later). >> >> 3. I'd also like them to be able to fill in information that I request >> from them that I can backfill later. Things like names of secretaries >> for new doctors or times for new appointments. >> >> What options do I have for doing this in OrgMode?? > > You might look into nikola: > - https://plugins.getnikola.com/v7/orgmode/ > Thanks. I'll give it a look. -- David
Re: [O] org-habit: allow overriding org-scheduled-past-days and always including time of day
Hello, John Lee writes: > Here's a couple of patches that add new org-habit variables. I hope > the variable documentation describes them sufficiently: if not I need > to change the docs so if you review these patches please read the > patch before the rest of this email so that you're not "cheating"! Thank you. Some comments follow. > My own workflow around this is similar to GTD, so I'm using SCHEDULED > as basically a way to get TODO items to show up after the scheduled > date, not to show up in the calendar except as a reminder that I have > new TODOs. For that reason I set org-scheduled-past-days to a low > value (3 right now). I also set org-agenda-todo-ignore-scheduled to > 'future and org-agenda-tags-todo-honor-ignore-options to t (not > directly relevant here except as context). For habits that causes > habits not to show up sometimes because of the short > org-scheduled-past-days, which isn't appropriate for my habits: if > I say .+5d, I still want to see the habit there if it's due, even if > it's been 4 days since the last done date (which is more than the > 3 days of org-scheduled-past-days). This motivates > `org-habit-scheduled-past-days'. It sounds reasonable. > Similarly, since I want to do some of my habits at a particular time > of day, org-agenda's omitting of the time of day from the scheduled > timestamp if this is a "repeat" (i.e. I missed doing the habit) is > unhelpful for habits, because now I have to scan though a long-ish > list of habits (5 or 10 right now!) and think "is now the right time, > should I have done that already?" for every habit in the list, rather > than just eyeballing it to see which ones are around now in time. This > motivates `org-habit-always-show-time'. It sounds good too. However, I wonder if that shouldn't be the default. Hiding the time for a missed scheduled item hadn't the habits in mind (see http://lists.gnu.org/archive/html/emacs-orgmode/2016-11/msg00539.html). To put it differently, is there any workflow wanting to hide the time for habits in this case? > I have not yet submitted the FSF copyright assignment form but am > prepared to do so. This can go as a TINYCHANGE (you need to put that string at the end of the commit messages). However, if you plan to be able to provide more code to Org, I suggest starting the copyright assignment nonetheless. > * lisp/org-habit.el: Add new variable `org-habit-scheduled-past-days' > to allow overriding `org-scheduled-past-days' for habits It should simply be: * lisp/org-habit.el (org-habit-scheduled-past-days): New variable. > (when (or (and (> ddays 0) (< diff ddays)) > - (> diff org-scheduled-past-days) > + (> diff (if habitp > + (or org-habit-scheduled-past-days > + org-scheduled-past-days) > + org-scheduled-past-days)) Nitpick: (or (and habitp org-habit-scheduled-past-days) org-scheduled-past-days) > +(defcustom org-habit-scheduled-past-days nil > + "Non-nil means the value of this variable will be used instead > +of org-scheduled-past-days, for habits only. First line needs to be a full sentence. Also, `org-scheduled-past-days' > +Setting this to say 1 is a way to make habits always show up > +as a reminder, even if you set org-scheduled-past-days to a small Ditto: `org-scheduled-past-days'. > +value because you regard SCHEDULED items as a way of 'turning on' scheduled items "turning on" > +TODO items on a particular date, rather than as a means of > +creating calendar-based reminders." as a mean of... > + :group 'org-habit > + :type 'integer) You need to add :package-version and :safe keywords. > * lisp/org-habit.el: Add new variable `org-habit-always-show-time' > to force always showing the time of day See above. > * lisp/org-agenda.el (org-agenda-get-scheduled): honour > `org-habit-always-show-time` > --- > lisp/org-agenda.el | 12 +--- > lisp/org-habit.el | 10 ++ > 2 files changed, 19 insertions(+), 3 deletions(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index e2bd5cc2d..08e286730 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -6253,9 +6253,15 @@ scheduled items with an hour specification like > [h]h:mm." > (head (buffer-substring (point) (line-end-position))) > (time > (cond > - ;; No time of day designation if it is only > - ;; a reminder. > - ((and (/= current schedule) (/= current repeat)) nil) > + ;; No time of day designation if it is only a > + ;; reminder (unless org-habit-always-show-time > + ;; forces display of the time of day > + ;; designation). > + ((and > +(not (and habitp org-habit-always-show-time)) > +(/=
Re: [O] Getting feedback from a website created with OrgMode ??
On Sun, Nov 18, 2018 at 4:54 PM David Masterson wrote: > > I'd like some ideas on how to create a website with OrgMode. OrgMode is > very good at creating static web-pages of any sort of structure. What I > think I'd like to do is create a more dynamic web-page. My particular > use-case is the following: > > 1. I'd like to create a website of information for my family of calendar > information and financial information that they might need in day to day > keeping track of family needs. > > 2. I'd like the family to be able to comment on the information as > needed to let me know if something is wrong or missing. This might be a > comment at the bottom of the web-page or an email feedback with a tag of > the particular web-page (so I can find it later). > > 3. I'd also like them to be able to fill in information that I request > from them that I can backfill later. Things like names of secretaries > for new doctors or times for new appointments. > > What options do I have for doing this in OrgMode?? You might look into nikola: - https://plugins.getnikola.com/v7/orgmode/ I've used it and think it's pretty awesome. I *haven't* used comments, but they look possible: - static: https://getnikola.com/blog/really-static-comments-with-staticman.html - more "standard" options mentioned: https://oliver2213.me/posts/self-hosted-comments-with-nikola/ Not sure on what you want in #3 exactly. Like fill in a form and store the answer? Or have a blank in the exported document that you somehow store/get/use later? It brings to mind input fields you could have emailed to you, or piping those into a database? The main point was to make you aware of nikola if you hadn't heard of it... John > > -- > David Masterson >
[O] Getting feedback from a website created with OrgMode ??
I'd like some ideas on how to create a website with OrgMode. OrgMode is very good at creating static web-pages of any sort of structure. What I think I'd like to do is create a more dynamic web-page. My particular use-case is the following: 1. I'd like to create a website of information for my family of calendar information and financial information that they might need in day to day keeping track of family needs. 2. I'd like the family to be able to comment on the information as needed to let me know if something is wrong or missing. This might be a comment at the bottom of the web-page or an email feedback with a tag of the particular web-page (so I can find it later). 3. I'd also like them to be able to fill in information that I request from them that I can backfill later. Things like names of secretaries for new doctors or times for new appointments. What options do I have for doing this in OrgMode?? -- David Masterson
Re: [O] Local COLUMNS and columnview block
Nicolas Goaziou writes:
> Lele Gaifax writes:
>
>> As said, a the local COLUMNS setting is honored by the transient columns
>> view,
>> but it is ignored by org-clock-report and org-dbclock-update.
>>
>> Am I doing something wrong or isn't it possible?
>
> COLUMNS property, or keyword, are not related to clocktable and such.
>
> Moreover, in the "columnview" dynamic block, you use ":id global", which
> means calling `org-columns' on the whole buffer, using global COLUMNS
> keyword.
Thanks for confirming that.
> You can use :format property to use the appropriate columns:
>
> :format "%40ITEM(Item) %13Effort(Effort){:} %CLOCKSUM(Spent)"
>
Nice, that fits my need, and I completely missed the ":format" argument!
Thanks a lot,
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
l...@metapensiero.it | -- Fortunato Depero, 1929.
Re: [O] FW: [RFC] Link-type for attachments, more attach options
Hi, > -Original Message- > From: Ihor Radchenko > Sent: den 18 november 2018 01:42 > To: Gustav Wikström ; Marco Wahl > > Cc: emacs-orgmode > Subject: RE: [O] FW: [RFC] Link-type for attachments, more attach options > > Hi Gustav, > > > I like the idea of a function that would symbolically links folders > > from "ID"-folder structure to a hierarchy-folder structure, based on > > the name and path of the org-file and its headings containing the > > links. I probably wouldn't use it much myself though. Not until > > org-mode starts working better with multiple files, allowing us to > > more easily define "org-mode libraries". > > I am wondering what you mean by "org-mode libraries". Can you explain > further? This goes a bit off topic; But what I mean is mainly two things: 1) Generalize the org-agenda so that we can have multiple ones Generalize org-agenda by allowing us to have multiple ones, and make them more general by thinking of them as a set of views that works on sets of files. Maybe this is not for all, but I would appreciate to create multiple "agendas" (even though I'd call them "libraries" in instead), and possibly also an aggregate agenda consisting of other agendas. 2) Make files function as virtual "level-0 headings" If two org-mode files exist in the same folder with different names, it would be awesome to think of (and work with) them as two top-level headings inside one org-mode buffer. Similar to two level-1 headings inside an org-mode file. For this to work all properties we can define for regular headings should be possible to define for these "level-0 headings". For example an attachment-folder or ID, a deadline, scheduled date, or TODO-keyword should in that case be configurable on the whole file. I guess some new conventions regarding syntax and existing properties would have to be created as well. > > Also, another thought about the attachment: links. > It would be useful to implement links to attachments, which are not in the > current org entry. > For example, something like "attachment:ORG-ID:file-name", where ORG-ID > refers to ID of an arbitrary org entry. I wouldn't call that attachment-links, but rather ID-based links (since attachments are local based on either headline ID or attach-dir of the current headline). ID links exist already but link to headlines. If you rather see ID-based attachments as some kind of global attachments for all your org-mode files, I'd think the link-type should reflect that and be called something like "ID-attachment:file-name", "ID-@:file-name", "@ID:file-name" and be a separate link-type. > > Best, > Ihor > > Kind regards Gustav
