Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
Hi Charlie, On Di, 2017-09-26 at 19:22, Charles Millar wrote: > A. Persons Name is exported as > > 1. Persons Name > > not > > A. Persons Name. What about marking as verbatim? =A. Person= Best regards Michael Strey -- http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Beamer_act property is misnamed in org-mode Ubuntu package
On Wednesday, 27 Sep 2017 at 11:53, James Harkins wrote: > Hi, > > There seems to be a mistake in the org-mode Ubuntu 16.02 packages. > > For beamer, if I C-c C-x p to add a property, one of the predefined options > is: > > :BEAMER_act(Act): 1 I think (could be wrong on this) that org includes any properties you already have as pre-defined options available to you. Maybe you have this property already in your file? -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302 signature.asc Description: PGP signature
Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
On Tuesday, 26 Sep 2017 at 19:22, Charles Millar wrote: > For example > > A. Persons Name is exported as > > 1. Persons Name You must have set org-list-allow-alphabetical to non-nil... maybe turn this off? -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302 signature.asc Description: PGP signature
Re: [O] How to generate clock report for hours worked each day?
On Tuesday, 26 Sep 2017 at 18:27, ConcreteVitamin wrote: > Following up on this: is there a way to configure such that non-clocked in > files (0:00) are not shown in this table? I don't get non-clocked files shown. What version of org are you using? Maybe post what you get? -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302 signature.asc Description: PGP signature
[O] Beamer_act property is misnamed in org-mode Ubuntu package
Hi, There seems to be a mistake in the org-mode Ubuntu 16.02 packages. For beamer, if I C-c C-x p to add a property, one of the predefined options is: :BEAMER_act(Act): 1 But it should be :BEAMER_act: 1 The former is ignored in the generated LaTeX. The latter produces a correct overlay spec. Is that still the case in the most recent org release? If yes, I'd like to file it as a bug report. If not... I guess it's time to dump the Ubuntu packages. hjh
[O] How to suppress latex exporting as a list if a name that begins with a single letter
For example A. Persons Name is exported as 1. Persons Name not A. Persons Name. Charlie Millar
Re: [O] Inline source does not evaluate when inserted insie a minipage environment
On 09/25/17 03:32, Eric S Fraga wrote: On Sunday, 24 Sep 2017 at 16:59, Charles Millar wrote: You might also want to consider using special blocks which could be a more general solution: #+attr_latex: :options [t]{4.0in} #+begin_minipage This is some text. Some more test with an inline src_sh[:results raw]{echo 1} a bit more #+end_minipage Thanks again, I am using this suggestion. Charlie Millar
Re: [O] orgmode for many continuous tasks?
Hello Eric. [...] Plausible (or implausible) solutions to my problem or to Mycroft's are hereby solicited. On the right track, but perhaps wrong scale. What you need is to embrace the exciting possibilities of augmented reality! [...] The answer is obvious: a clipboard! It's rugged and inexpensive. [...] It's remarkably calming. It's nice just to have something physical to look at. 200% agree. :) + In the electronic realm, nothing better than orgmode. + In the physical world, nothing better than a board (for groups) and the faithful midori traveler's notebook (for personal things). Best... -- eduardo mercovich Donde se cruzan tus talentos con las necesidades del mundo, ahí está tu vocación. (Anónimo)
Re: [O] orgmode for many continuous tasks?
Mycroft Jones writes: > Getting in the habit of being away from the computer is good. Getting > in the habit of reviewing the days events at the end of it is also > good. Hear hear!
Re: [O] How to generate clock report for hours worked each day?
Following up on this: is there a way to configure such that non-clocked in files (0:00) are not shown in this table? On Mon, Sep 25, 2017 at 12:39 AM Eric S Fraga wrote: > On Monday, 25 Sep 2017 at 03:58, ConcreteVitamin wrote: > > Thanks! This workflow works. > > > > I can't help but wonder, does my use case show that in org-mode > philosophy, > > tasks are best filed under a plain entry, not within a datetree? > > I would say that the org-mode philosophy is what works for you is > perfect! > > My own workflow is that I use a date tree for "short" tasks, those that > will be done usually well within a single day's activity. Longer tasks > are "projects" and they tend to have their own full structure. E.g. I > have main headlines for teaching, research, and admin and I clock into > those while my date tree will be things like "Meet with student X", > "submit proposal", "prepare agenda for meeting", etc. > > But everybody does things differently and that is the best thing about > org: it doesn't impose any particular approach. > > -- > : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302 >
Re: [O] Bug: Remote column editing from agenda is broken [9.1.1 (9.1.1-6-gd40deb-elpa @ /Users/bnbeckwith/.emacs.d/elpa/org-20170925/)]
Hello, Benjamin Beckwith writes: > Given a list of agenda files, I can bring up a global view of all > tasks. Then, if I enter into column mode and try to edit one of the > columns (say priority), it complains about the marker. > > My config is the minimal one found on > http://orgmode.org/manual/Feedback.html. The agenda file I used is very > simple. > > * TODO One * TODO Two * TODO Three > > > I then add this to the agenda file list. And then use 'org-agenda' > followed by 't' to bring up a list of all todo items. I enter into > column mode and place my cursor into the PRIORITY column. When I try to > press '1' to change the priority, I get the following stack trace. > > The stack trace is: > > Debugger entered--Lisp error: (wrong-type-argument markerp nil) Fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] orgmode for many continuous tasks?
On Tue, Sep 26, 2017 at 01:30:35PM +0300, Melleus wrote: The answer is obvious: a clipboard! It's rugged and inexpensive. I've actually done this a few times, when I've been using Org to organize event management and was out of the office all day long. Printed out my daily agenda in the morning, made notes on the clipboard throughout the day, and entered changes into the computer at the end of day. Yes, I said the same to Peter in private email. And, if you print off your list, it gets depressing because it is SO long, longer than you could hope to accomplish in a day. That is why I'd like the algorithm to take into account the time budget, and only put on a number of things that add up to 8 hours. So, some items are done in 1/2 hour chunks, others in 2 hour chunks, all good. That way you have a daily task list and can feel good accomplishment if you clear up your list for the day. Maybe it's a bit overhead, but anyway. You can use org-caldav-sync to sync the todos with local owncloud (or other caldav) server and use some phone/tablet's calendar to sync with owncloud to have your tasklist with you on the run and you can use it for capturing todos also, as the two-way sync is no problem for org-caldav-sync. When you're up on a roof, or driving a tractor, or shearing a sheep, a cell phone can be destroyed very quickly. Last thing you need is it dropped into the mud and stepped on by a heavy ungulate. Clipboard is cheap, and you can always print out your list again. Getting in the habit of being away from the computer is good. Getting in the habit of reviewing the days events at the end of it is also good. Mycroft
Re: [O] Confused about the explanation for 'org-cycle'
Nicolas Goaziou writes on Tue 26 Sep 2017 12:41: > Hello, > > alain.coch...@unistra.fr writes: > > > But now, compared to the previous version: > > > >When the cursor is at the beginning of the buffer and the > >first line is not a headline, then actually runs global > >cycling > > > > it is not clear to me why the mention "and the first line is not > > a headline" has been suppressed. > > I traded completeness for clarity. > > The reasoning is that the description about a pathological case -- > here, the first line of the buffer being a heading -- belongs to > variable's docstring, not to the manual. > > We can add a footnote about that case, but even a footnote impedes > clarity. > > Of course, if you have a clear wording that includes that > pathological case, I'll happily use it. OK, I understand your point, although I probably cannot fully appreciate it because I do not know what a "docstring" is. As for the wording, I have nothing ecstatic to propose, but -- as a beginner and trying to think like one who is reading the manual for the first time while experimenting -- I would have been happy with something like: You can run global cycling using only if point is at the very beginning of the buffer (not being a headline) and `org-cycle-global-at-bob' is set to a non-`nil' value. More generally, I cannot remember the number of times when I read the manual, do not understand it, am essentially sure that it is wrongly phrased but (just in case) spend a (too) long time searching the Web before complaining to the list, to finally realize that "Ah OK, the manual is fully correct." In other words, the manual is often too concise/elegant for the (admittedly not very smart) beginner that I am, and I would favor completeness -- with footnotes, dumb examples to get started, more cross-references, even repetitions -- over clarity. But maybe that's just me... Regards, a. -- EOST (École et Observatoire des Sciences de la Terre) IPG (Institut de Physique du Globe) | alain.coch...@unistra.fr 5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44 F-67084 Strasbourg Cedex, France| Fax: +33 (0)3 68 85 01 25
Re: [O] Confused about the explanation for 'org-cycle'
Hello, alain.coch...@unistra.fr writes: > But now, compared to the previous version: > >When the cursor is at the beginning of the buffer and the first >line is not a headline, then actually runs global cycling > > it is not clear to me why the mention "and the first line is not a > headline" has been suppressed. I traded completeness for clarity. The reasoning is that the description about a pathological case -- here, the first line of the buffer being a heading -- belongs to variable's docstring, not to the manual. We can add a footnote about that case, but even a footnote impedes clarity. Of course, if you have a clear wording that includes that pathological case, I'll happily use it. Regards, -- Nicolas Goaziou
Re: [O] orgmode for many continuous tasks?
Eric Abrahamsen writes: > Tim Cross writes: > >> Peter Neilson writes: >> >>> >>> * TODO Devise a way to project my agenda (in unavoidable brilliance) onto >>> the side of the barn, or perhaps embroider it into the fleece of my sheep >>> (who * TODO need to be shorn). >>> >>> Plausible (or implausible) solutions to my problem or to Mycroft's are >>> hereby solicited. >> >> On the right track, but perhaps wrong scale. What you need is to embrace >> the exciting possibilities of augmented reality! A pair of glasses where >> whenever you look at something which has a related todo or note in your >> org files, displays the item in a little box linked to that item. > > The answer is obvious: a clipboard! It's rugged and inexpensive. > > I've actually done this a few times, when I've been using Org to > organize event management and was out of the office all day long. > Printed out my daily agenda in the morning, made notes on the clipboard > throughout the day, and entered changes into the computer at the end of > day. > > It's remarkably calming. It's nice just to have something physical to > look at. > > Eric Maybe it's a bit overhead, but anyway. You can use org-caldav-sync to sync the todos with local owncloud (or other caldav) server and use some phone/tablet's calendar to sync with owncloud to have your tasklist with you on the run and you can use it for capturing todos also, as the two-way sync is no problem for org-caldav-sync.
Re: [O] Confused about the explanation for 'org-cycle'
Nicolas Goaziou writes on Wed 20 Sep 2017 12:57: > Hello, > > Matt Lundin writes: > [...] > I rewrote the part about `org-cycle-global-at-bob'. Hopefully it is > clearer now. Thank you, Nicolas and Matt, for the feedback. I updated to version org-20170925 and what I read now: You can run global cycling using only if point is at the very beginning of the buffer and `org-cycle-global-at-bob' is set to a non-`nil' value. is indeed fully clear to me concerning the issue I raised. But now, compared to the previous version: When the cursor is at the beginning of the buffer and the first line is not a headline, then actually runs global cycling it is not clear to me why the mention "and the first line is not a headline" has been suppressed. Perhaps it has been replaced by the addition of the word "very"? If so, I feel it is maybe a little bit less explicit. Regards, Alain -- EOST (École et Observatoire des Sciences de la Terre) IPG (Institut de Physique du Globe) | alain.coch...@unistra.fr 5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44 F-67084 Strasbourg Cedex, France| Fax: +33 (0)3 68 85 01 25