Ihor Radchenko writes:
> Robert Horn writes:
>
>>> Not really. Countries may change DST at any moment in future. Or decide
>>> to switch calendars (consider countries near the day transition line).
>>>
>>> And "past local time, according to the
wanted astronomical or other relationships would usually
specify UTC or TAI. They might use a fixed offset for UTC. People who
are into the demands of TAI (e.g., orbital mechanics) generally don't
want to deal with the offsets or other issues that come up with UTC, so
they wanted TAI.
--
Robert Horn
rjh...@alum.mit.edu
Ihor Radchenko writes:
> Robert Horn writes:
>
>>> 1. Time (-MM-DD HH:MM) not continuous and may change arbitrarily at
>>>certain times a year or in future or in the past:
>>>- DST transitions are not stable and change from year to year
>>>
is
is particularly tricky for repeating times for regularly scheduled events.
> 5. Leap seconds! 23:59:59 -> 23:59:60 -> 00:00:00, according to
>astronomical Earth observations
>
Fortunately, the most recent vote reached majority for eliminating leap
seconds, hopefully within 8 years.
--
Robert Horn
rjh...@alum.mit.edu
They both have org-mode integrations. E.g., create an org-mode task
from within the email reader, with link back to the email.
--
Robert Horn
rjh...@alum.mit.edu
Colin Baxter writes:
>>>>>> Robert Horn writes:
>
> > Timothy writes:
>
> >> Ihor Radchenko writes:
> >>
> >> Maybe this is a good time to start a discussion about moving
> >> Org's minimum supported
robably not
cause too much breakage.
--
Robert Horn
rjh...@alum.mit.edu
use modifications of diary to insert sunrise and sunset.
But I think that these %% functiotns only show up as part of agenda processing.
--
Robert Horn
rjh...@alum.mit.edu
s from DIN 1355 and DIN 5008. It was changed to use
colons in 1995 to match ISO 8601. There are still many traditionalists
and old documents. Look for phrases like "6.30 Uhr" in old documents.
You will find a lot like that. I didn't like the dot notation and agreed
with
I've not pushed for these mostly because convenience typing military
time isn't worth figuring out all the changes that would be needed.
It's worth looking at all the issues discussed in ISO 8601 and
understanding them before you leap into time formatting changes. ISO
8601 is a compromise solution with lots of warts, but it is widely
supported and understood.
--
Robert Horn
rjh...@alum.mit.edu
The golang ical2org (https://github.com/rjhorniii/ical2org) definitely
does this.
--
Robert Horn
rjh...@alum.mit.edu
ese, but I can easily
write an elisp hook to capture the rules.
--
Robert Horn
rjh...@alum.mit.edu
roprietary platform. Git
was created due to problems with a dependency on a proprietary platform,
although in that case it was more related to a divergence in business
strategic directions than ethical issues.
--
Robert Horn
rjhorn...@gmail.com
that I've
revceived. It does not alway work right in applying the right time to an
event.
An example of my mu4e integration and systemd integration for google
synchronization is also documented.
--
Robert Horn
rjhorn...@gmail.com
y end. There is no error with org
9.1. Somehow that machine was never upgraded or got restored to an old
version. It was still on 8.2.
--
Robert Horn
rjh...@alum.mit.edu
but the
process is awkward. There is a lot of typing. Creating a little lisp
command for mu4e is likely the right solution.
--
Robert Horn
rjhorn...@gmail.com
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
margin.
Removing either the leading colon or the asterisk on example fixes the
problem.
Regular display parsing does not get confused. The highlighting and
font changes do not consider the " * example" to be a headline.
--
Robert Horn
rjh...@alum.mit.edu
Eric S Fraga writes:
> If you use gnus, it comes with a gnus-icalendar package which will
> convert calendar attachments to org entries. You can export to org &
> accept/decline events. I use this all the time.
I use mu4e, but I may steal from gnus-icalendar.
Thanks
--
Rober
ne(s) for the event and
put in the properties drawer. This allows a human to know what was
sent. I then assume that between the description, the zones, and the
times, a person can decide whether and how to adjust the active
timestamps in the org file.
--
Robert Horn
rjhorn...@gmail.com
Allen Li writes:
> On Mon, Jan 1, 2018 at 8:07 PM, Adam Porter wrote:
>
> I don’t see a use case for checking all heading data.
>
I can see such cases arising from templates and time tracking. I can
have a template that captures telephone calls. The call comes in and I
start the template. At
stardiviner writes:
> I have an org-mode file:
>
> #+begin_src org
> ,* Anniversary
>
> ,** my first child anniversary
>
> %%(diary-anniversary 10 26 2017)
>
> ,** Funeral Arrangement
>
> ,*** kk
>
> %%(diary-anniversary 12 8 2007)
> #+end_src
>
> How to include and show them in default org-agend
Peter Davis writes:
> Basically, I want to plot a time series graph showing my PSA (prostate
> specific antigen) over time. The PSA is measured at irregular intervals,
> and has been for over 4 years (and hopefully will continue for many more
> years.) That should be a simple enough graph. I've a
Nicolas Goaziou writes:
> Completeness is not possible. For example, we do not document every
> variable in the manual. Besides, when reading a pile of special rules
> for special cases, the reader may lose focus and miss the whole concept.
>
> BTW, a "docstring" is the documentation you get when
I'll note that I use %%( entries for sunset/sunrise, e.g.,
%%(diary-sunrise), and for some schedules that need logic that does "shift one
day if Monday is a holiday".
That means I will need the %%( functionality to keep working. I suspect
I'm not alone. These are some fairly old and stable func
I want to have sunrise and sunset in my time grid. I do this with two lines
with "%%(diary-sunrise)" and "%%(diary-sunset)" in them.
With the regular org-agenda this works, e.g.,
18:00..
weather:19:42.. Sunset (EDT) :
Bastien Guerry writes:
> Hi Philip,
>
> phillip.l...@russet.org.uk (Phillip Lord) writes:
>
>> I presume you do see this as an advantage? The issue is, surely,
>> that it's too much of a PITA for the advantage that you gain?
>
> Well, it's not really about PITA-or-not-PITA, it's just that I want
Eric S Fraga writes:
> On Monday, 8 May 2017 at 11:26, Nicolas Goaziou wrote:
>> Hello,
>>
>> I would like to scratch a long-standing itch and introduce the "c"
>> macro, which is basically a way to handle multiple counters in an Org
>> document. So, the following document
>
> This sounds like a
There is also a Firefox plugin "ScrapBook X", which is a successor to
Scrapbook. It can capture the web page alone (with links to outside
world) and allows you to select by depth or link additional pages
that are also to be captured. (If you have infinite time and storage
with the right links yo
I'm not enough of an ELPA guru to figure this out. I tried org-mode
9.0.1 using ELPA, found some issues I'll describe, and find that using
the direct git version does not have those issues.
All of this is with Emacs 24.5.2, GTK+ version 2.24.31. This is a fresh
setup, no other packages install
Konstantin Kliakhandler writes:
>
> Sufficient for what? I believe we were discussing security (that was my
> intention at least, and so did your previous email seem to indicate). And
> if this is the case, you have just contradicted yourself. I apologize for
> pointing it out so directly, and al
Konstantin Kliakhandler writes:
> Hello Robert,
>
> I am the OP.
>
> For what it is worth, the current discussion is actually precisely what I
> was aiming at. I agree with your analysis of my Intended goals but
> completely disagree that SHA1 alone is any sort of guarantee.. To be
> precise, I d
I think that the original question was looking at a different problem,
and discussion of hosted tooling may be a distraction. The issues that
normally come up for cyber-security discussions of distribution need to
be looked at. The following is a start at organizing those for
org-mode.
I think
>>> On 2016-03-18, at 17:51, Marcin Borkowski wrote:
>>>
I'm now reading org-read-date-analyze to be able to enable US military
format for hours (e.g., 2100 instead of 21:00). This is potentially
very useful (at least for me), since I'll be able to enter the hour with
This would
Robert Horn writes:
Apologies, sent to the wrong list
R Horn
--
Sent with my mu4e
Lisp error: (void-function add-face-text-property)
add-face-text-property(0 63 mu4e-header-face t #("08:31:05 PM S
Robert Horn+ testing" 0 11 (help-echo "Mon 25 Jan 2016 08:31:05
PM EST") 13 14 (help-echo "(seen)")))
mu4e~headers-line
Bastien Guerry writes:
> My simple point is: let's get more information and let's take a
> proper decision. Let's not force the change.
I took a look at what is presently supported by Red Hat, Ubuntu, and
OpenSuSE in their long term support releases. The results:
emacs 23.1 (RHEL 6.0, Ubuntu
Jay Iyer writes:
> If there are use cases out there, it might be worth collecting them and
> then thinking about how to support them better. If there aren't, maybe
> it should be thrown out.
It's most definitely useful. I'm not sure what you think would be
"better". I make extensive use of dat
I also use tables, and have one big recipe.org file. I considered
ingredient properties, etc., but ended up just text and find recipes by
using simple searches. They look like this:
* Texas Skillet Corn Bread
| Ingredient | Quantity | Instructions|
|+
I'm a user who doesn't much care about link following command behavior,
but Bastien's point about context is important. The behavior of a
command needs to depend upon much more than just syntax.
Two really dramatic examples are region narrowing and outline folding.
When operating on a narrowed r
Alan Schmitt writes:
> I can't promise anything, but I can try to write something. What
> external merging tool should I use?
>
There was some work done in a Summer of Code last year or the year
before. I don't know how much more work remains. It was an effort for
a delta operator for git.
I
Karl Voit writes:
> * David Rogers wrote:
>>
>> I agree that this kind of simple thing looks like a better
>> idea. However, it would also be nice to be able to call it some name
>> where a person who encounters the software capability but doesn't yet
>> know what it's for will understand what i
Erik Iverson writes:
> Robert,
>
> I noticed that behavior, too. But that does seem documented under M-:
>
> "When this command is used in the middle of a line, the line is split
> and the rest of the line becomes the new item or headline".
>
> Footnote 10 is referenced, which says:
>
> "If you d
I've noticed a probably related bug. In a file like
* before
break between
If I put the cursor between break and between, M-ret causes the result
* before
* break between
rather than what I expected:
* before
break
* between
With the holiday coming I might look at it also and figure out
I'm getting warnings about org-checklist that don't seem to be related
to any real problem. I've noticed no functional problems with
org-checklist.
This is with org elpa 20130522. I get the following warnings in
*Messages* when I change emacs color themes.
Auto-saving...done <--- harmless aut
Bastien writes:
> No objection of course, but it feels both formal and empty to me.
>
I share Bastien's opinion. My experience with community building is
that describing and rewarding exemplary behavior is much more useful
than attempting to set strict rules of behavior. You need some basic
ru
Achim Gratz writes:
> Jambunathan K writes:
>> Always use utf-8 for HTML export (No support for other coding systems).
>>
>> For or against. Please register your views.
>
> It is becoming more rare these days, but still possible that the
> document encoding cannot be UTF-8 for whatever reason.
Nicolas Goaziou writes:
> Hello,
>
> Robert Horn writes:
>
> As a rule of thumb, C-c C-c on a list will operate on every top level
> items and C-c C-c on a item will operate on the item. You are considered
> to be on a list when calling C-c C-c from affiliated keywor
Nicolas Goaziou writes:
> I plan to rewrite C-c C-c using Elements, so the behaviour will slightly
> change.
>
> It will be better to discuss about checkboxes when this change is done.
>
I've got no problem waiting, but it would be a good idea to figure out a
consistent non-contradictory key-bin
The keystroke bindings for lists need some examination and repair. In 7.9.3
the situation is:
| Keystrokes | First Item| Any other item
|
|-+---+---|
| C-c C-c | T
Nicolas Goaziou writes:
> Calling C-c C-c with an argument on the first item of a list or sub-list
> will apply the change on every item in the list. It looks consistent
> with what you get.
>
> What did you expect instead ?
>
I was expecting the single checklist item to go to "[-]". On all ot
There is a bug in checklist handling. The following list will show the problem.
1. [ ] Use Cases
2. [ ] Threat Model
3. [ ] ITI Wiki
4. [ ] Maynard stuff
5. [ ] Annual Transition
- wiki changes
- ftp changes
Context:
Org-mode version 7.9.3a (release_7.9.3a @
/ho
Eric Schulte writes:
> That sounds like it should work, although I would go with the more
> complete but possibly overkill
>
> ;; emacs-lisp
> (package-initialize)
> (require 'org)
> (org-reload)
>
> Let me know if either of the above is sufficient to solve your problem
> and ensur
Bastien writes:
>
> I also wish Emacs can read an ~/.emacs.org init file.
>
That is what the starterkit for emacs 24 is attempting to do. It's got
a ~/init.el that is just
#+begin_src emacs-lisp
(setq starter-kit-dir
(file-name-directory (or load-file-name (buffer-file-name
;; load up
Achim Gratz writes:
> Robert Horn writes:
>> I'm experimenting with starterkit on a new machine and have run into a
>> bug in org-mode elpa version 20121231.
>
> Using two systems that hook into Emacs' startup sequence simultaneously
> is asking for trouble.
Robert Horn writes:
> I'm experimenting with starterkit on a new machine and have run into a
> bug in org-mode elpa version 20121231.
>
> With the stock distribution org-mode (7.8.11) in emacs 24.2 there is no
> problem. With the elpa version 20121231 I get an error, see t
I'm experimenting with starterkit on a new machine and have run into a
bug in org-mode elpa version 20121231.
With the stock distribution org-mode (7.8.11) in emacs 24.2 there is no
problem. With the elpa version 20121231 I get an error, see the
attached output from emacs --debug-init.
It's not
FBastien writes:
> Robert Horn writes:
>
>> I think that the key mapping for "," and "C-c," in agenda is a mistake
>> and should be swapped.
>
> The agenda is read-only, so short keystrokes are often preferred
> over long one. "," be
I forgot to attach a proposed patch. This changes the keymapping for
"C-c ," to use org-agenda-priority. It doesn't include a new keymapping
to org-agenda-show-priority. I'm not sure what key mapping makes the
most sense. It leaves the agenda menu and mouse functions for
org-agenda-show-priorit
I think that the key mapping for "," and "C-c," in agenda is a mistake
and should be swapped. In the normal org-mode, "C-c ," is mapped to
org-priority. In agenda mode this gets changed to
org-agenda-show-priority. In agenda mode "," is mapped to
org-agenda-priority, which behaves like org-priori
Alan Schmitt writes:
> Eden Cardim writes:
>
>>> "Alan" == Alan Schmitt writes:
>> Alan> Do you have a reliable system to link to emails? I've been
>> Alan> working on this and I'm not too satisfied yet.
>>
>> Not sure what you mean by reliable. I use offlineimap to sync my mail
>>
Memnon Anon writes:
>
> I think the consistency bar is only fully functional with timestamps
> of the format <2012-09-13 Do .+7d/10d> : You need a minimum/maximum range.
>
Thank you. That was the clue I needed. I hadn't made the connection
between schedule repeat intervals and deadlines in hab
Bastien writes:
>>
>> Habit: HABIT [#A] Weekly GTD revi * !
>> :home:
>
<>
Is what it looks like (a day later).
R Horn
rjh...@alum.mit.edu
I'm trying to get some habits set up that have a regular time window
during which I should do them. The habits are being created and
somewhat maintained, but the habit bars are not acting the way that I
expected.
In the org file I have:
*** HABIT [#A] Weekly GTD review [0/9]
I found the issue, and it's a more subtle one. I've set a bug to emacs
list in case they think it's a documentation or fixable bug. What
happens is this:
- The custom value setting for org options do not take effect until *after*
the relevant lisp code has been executed once. This means:
There is more to this bug. I don't think there is a problem with my
patch, but it doesn't fix it on all systems. It fixed things on my Mac,
but not on Linux or Windows.
Blessed with a lack of understanding for exactly what is going on I find
that changing the line in .emacs for custom-set-vari
This patch fixes my problem, but indicates that there is a startup
sequencing issue that may also affect other parts of org.
First the patch
--- org-agenda.el~ 2012-09-12 21:24:27.0 -0400
+++ org-agenda.el 2012-09-17 06:02:45.0 -0400
@@ -90,7 +90,7 @@
(defvar org-mob
Charles Philip Chan writes:
> Jude DaShiell writes:
>
> Hi Jude:
>
>> It might be near time to investigate wunderground.com and loose google
>> for weather before igoogle disappears. Other weather sites capable of
>> text output may also be available, I haven't investigated that yet.
>
Followu
Charles Philip Chan writes:
> Jude DaShiell writes:
>
> Hi Jude:
>
>> It might be near time to investigate wunderground.com and loose google
>> for weather before igoogle disappears. Other weather sites capable of
>> text output may also be available, I haven't investigated that yet.
>
wunderg
On Wed, Aug 29, 2012 at 08:00:18PM +0200, Bastien wrote:
> Hi Achim,
>
> Achim Gratz writes:
>
> > Achim Gratz writes:
> >> Can we see the full output, please?
> >
> > I got a mail from Robert (apparently not sent to the list) that the
> > error was related to his use of some stuff in contrib/,
A bug, perhaps ELPA related. Sorry to be so brief but I've got to run
soon to the station. I'm going to be tied up for the next week, but if
it's not figured out by then, I'll have time to look in more detail.
I confirmed this on Linux, Mac, and Windows, all emacs 24.1. All
respond the same.
Separating out the issue of how to hide and expose the content, why not
use s-expressions for the hidden content? Org is built on a lisp engine
and these will fit nicely into automation. It avoids a lot of parsing
and other headaches, and an s-expression can hold any of the discussed
information
Jonathan Leech-Pepin writes:
> Hi,
>>> This blocks could be hidden under all normal means unlike
>>> really someone want to see them and hit a special
>>> key-combo.
>>
>> Hmm, personally I'd rather have it visible but clearly
>> labeled. Transparency is nearly always a good thing.
>>
>
I agree.
he issue of how
to manage such archival is one that I haven't given much thought, since
disk space is cheap and it's easy to collapse the old stuff.)
Robert Horn
Another area that would be nice to address is taking advantage of the
information in date-trees so assist with merging. This is similar to
the logic around keeping headlines in order. With date trees there is a
date and sometimes time tag to help.
In addition to the occurrence order, there is al
Is there a short simple key sequence that will take you to the last
entry in a date-tree and open that headline? Slightly better would be a
way to go to the last, and open the last N headlines. It could be
generalized into "go to end of current item and open last N items of
whatever depth" wh
> So I am not sure what 64 bit systems do now or in the future, but
> it seems that we need to live with a restriction for now.
> Maybe this should be documented somewhere.
>
> - Carsten
Most 64-bit systems use a 64-bit int. All of the 64-bit Linux systems
that I've used use a signed 64-bit int
I wanted to set up a regular meeting that would appear in the agenda
grid. I discovered that the following works:
... Regular Meeting 13:00-14:00
<%%(diary-float t 2 1)>
This creates a first tuesday of each month meeting, from 1300h to 1400h.
This works because the default for the
org-agenda-sea
I tracked down the problem I was seeing. It's unrelated to habits. I
just connected it with habits because it affects them, as well as other
things.
The default behavior of the built-in agenda is to set the point in the
agenda to be today. This is not the default for custom commands. The
close
On 11/11/2010 07:07 AM, Matt Lundin wrote:
> Robert Horn writes:
>
>> I just noticed the following oddity.
>>
>> 1.) I have a custom agenda that consists of:
>>
>> (setq org-agenda-custom-commands
>> '(("h" "Agenda and Th
I just noticed the following oddity.
1.) I have a custom agenda that consists of:
(setq org-agenda-custom-commands
'(("h" "Agenda and This Week tasks"
((agenda "")
(todo "THISWEEK")
2.) I have the default agenda period of 1 week at startup.
The behavior I see is:
a
On 10/25/2010 02:18 AM, Carsten Dominik wrote:
> Hi,
>
> I have the feeling that there are really two strands of
> discussion going on here.
>
> 1. A two-level or even hierarchical way to *enter* *normal* tags,
>i.e. tags that are specified in the headline of a node.
>
> 2. A complex new str
On 10/16/10 4:09 PM, Carsten Dominik wrote:
>
> On Oct 16, 2010, at 9:26 PM, Robert Horn wrote:
>
>> On 10/16/2010 01:32 AM, Carsten Dominik wrote:
>>>
>>> On Oct 15, 2010, at 4:43 PM, Ilya Shlyakhter wrote:
>>>
>>>> Karl Maihofer gmx.de>
On 10/16/2010 01:32 AM, Carsten Dominik wrote:
>
> On Oct 15, 2010, at 4:43 PM, Ilya Shlyakhter wrote:
>
>> Karl Maihofer gmx.de> writes:
>>> Besides that I have tags in other contexts, e.g. GTD-related tags etc.
>>> So it would be very useful to be able to group the tags as it is
>>> possible f
On 09/29/2010 12:07 PM, Carsten Dominik wrote:
> Hi Robert,
>
> would you like to formulate a patch to org.texi?
>
This is my proposed patch. I hope I've done this right.
*** org.texi2010-10-06 09:06:20.0 -0400
--- org.texi-original 2010-07-21 12:42:48.0 -0400
I've been using habits and found additional uses that are actually
implemented but not mentioned in the documentation. What I've found
useful are:
1) Using a '++' repeat style for habits that have calendar constraints.
I use this for some activities that must be done on Monday, or on
weekends.
I ran into this, so I'll warn others. It might belong in the notes for
org-7.01.
If you have a newer version of emacs that has org already integrated,
you get some, but not all, of the org-7.01 features functioning if you
have org-7.01 set as the auto-load directory. I had been using org by
havi
87 matches
Mail list logo
