I have looked into it further, it is a bug in the move-to-column
function
in XEmacs that does not behave well in combination with hidden text,
when the FORCE argument is given.
Maybe you can try to write a replacement that will work?
- Carsten
On Feb 26, 2008, at 6:13 PM, Tim O'Callaghan wrote
On Feb 28, 2008, at 3:05 AM, Wanrong Lin wrote:
Bastien wrote:
Bernt Hansen <[EMAIL PROTECTED]> writes:
Maybe use SCHEDULED: instead of DEADLINE: ?
I'm afraid this won't solve Wanrong's problem: you don't get warned
about scheduled items.
Wanrong: maybe you can turn your items into sche
On Feb 28, 2008, at 3:16 AM, Wanrong Lin wrote:
Bastien wrote:
Wanrong Lin <[EMAIL PROTECTED]> writes:
I have the following in my org-mode configuration:
(setq org-return-follows-link t)
This is about following links, no (un)folding subtrees...
Yes, but only with this setting will ke
Hi Bastien,
I tried the newer version and it works. Great!
Thanks.
--
Kondo Kenji
At Thu, 28 Feb 2008 01:14:34 +,
Bastien wrote:
>
> Hi Kondo,
>
> Kondo Kenji <[EMAIL PROTECTED]> writes:
>
> > Hmm. I tried the git version but timestampes didn't work with C-c C-e P
> > when `org-publish
Wanrong Lin wrote:
Thanks a lot for the suggestions, but manual workaround does not work
for me, as I want org to take care of giving me a notification in
advance in the agenda buffer.
For SCHEDULED and plain active time stamp, I don't think we need to
have a default ahead notification s
Bastien wrote:
Wanrong Lin <[EMAIL PROTECTED]> writes:
I have the following in my org-mode configuration:
(setq org-return-follows-link t)
This is about following links, no (un)folding subtrees...
Yes, but only with this setting will key be added to the
"org-mouse-map" key map,
Bastien wrote:
Wanrong Lin <[EMAIL PROTECTED]> writes:
I found something really strange:
Whenever I do a search (either "tags-todo" search, or "todo" search),
as long as the search result contains an entry with tags, the
"*Messages*" buffer will generate a message like this:
Invalid face r
Bastien wrote:
Bernt Hansen <[EMAIL PROTECTED]> writes:
Maybe use SCHEDULED: instead of DEADLINE: ?
I'm afraid this won't solve Wanrong's problem: you don't get warned
about scheduled items.
Wanrong: maybe you can turn your items into scheduled items and then use
`org-check-before-da
Bastien <[EMAIL PROTECTED]> writes:
> Bernt Hansen <[EMAIL PROTECTED]> writes:
>
>> Maybe use SCHEDULED: instead of DEADLINE: ?
>
> I'm afraid this won't solve Wanrong's problem: you don't get warned
> about scheduled items.
Oops. You're right - I should have tested that first.
Thanks for the c
Wanrong Lin <[EMAIL PROTECTED]> writes:
> I have the following in my org-mode configuration:
>
> (setq org-return-follows-link t)
This is about following links, no (un)folding subtrees...
> Usually, if my cursor is at the beginning of a heading, I can use the
> return key to cycle the visibility
Wanrong Lin <[EMAIL PROTECTED]> writes:
> I found something really strange:
>
> Whenever I do a search (either "tags-todo" search, or "todo" search),
> as long as the search result contains an entry with tags, the
> "*Messages*" buffer will generate a message like this:
>
> Invalid face reference:
Bernt Hansen <[EMAIL PROTECTED]> writes:
> Maybe use SCHEDULED: instead of DEADLINE: ?
I'm afraid this won't solve Wanrong's problem: you don't get warned
about scheduled items.
Wanrong: maybe you can turn your items into scheduled items and then use
`org-check-before-date' in the relevant file
Hi Kondo,
Kondo Kenji <[EMAIL PROTECTED]> writes:
> Hmm. I tried the git version but timestampes didn't work with C-c C-e P
> when `org-publish-use-timestamps-flag' is t.
>
> Is it OK in your environment?
I just tested it and it seems okay.
Can you make sure there is no old `org-publish.el' h
Thanks :)
Bastien <[EMAIL PROTECTED]> writes:
> Hi Bernt,
>
> Bernt Hansen <[EMAIL PROTECTED]> writes:
>
>> 10 asterisks is only 6 levels deep when odd levels only are used.
>> This increases the number of asterisks to 40 (still an arbitrary number)
>> but it's much larger than the current limit
Hi Bernt,
Bernt Hansen <[EMAIL PROTECTED]> writes:
> 10 asterisks is only 6 levels deep when odd levels only are used.
> This increases the number of asterisks to 40 (still an arbitrary number)
> but it's much larger than the current limit of 10.
Thanks for the patch.
I applied it, but used a
Bernt Hansen <[EMAIL PROTECTED]> writes:
> The following variables set to behaviour
set to -> set the
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/ema
It's configurable (as is almost anything else in Emacs)
The following variables set to behaviour
appt-message-warning-time (12 minutes for me)
appt-display-interval ( 3 minutes for me)
I get warnings at 12, 9, 6, 3, and 0 minutes.
HTH,
-Bernt
Russell Adams <[EMAIL PROTECTED]> writes:
Ok, so how far in advance is appt supposed to alert you?
I'm testing this, and I've gotten zenity to do a popup, and I've tied
the refresh of the appt list to the agenda refresh with:
(add-hook 'org-finalize-agenda-hook 'my-org-agenda-to-appt)
I'm testing a series of timings before I start relyi
10 asterisks is only 6 levels deep when odd levels only are used.
This increases the number of asterisks to 40 (still an arbitrary number)
but it's much larger than the current limit of 10.
This fixes C-c C-x C-d when trying to summarize clock time on a
deeply nested task
,[ test.org ]
| * T
Hi Carsten,
I ran into another bug a few minutes ago.
,[ test.org ]
| #+STARTUP: odd
| * Task1
| *** Task2
| * Task3
| *** Task4
| * Task5
| *** Task6
| :CLOCK:
| CLOCK: [2008-02-27 Wed 14:30]--[2008-02-27 Wed 14:44] => 0:14
| :END:
`
Hmm. I tried the git version but timestampes didn't work with C-c C-e P
when `org-publish-use-timestamps-flag' is t.
Is it OK in your environment?
--
Kondo Kenji
At Wed, 27 Feb 2008 16:14:40 +0100,
Carsten Dominik wrote:
>
> Thanks, I believe this is now fixes as well, please let me know if no
Hi,
I found something really strange:
Whenever I do a search (either "tags-todo" search, or "todo" search), as
long as the search result contains an entry with tags, the "*Messages*"
buffer will generate a message like this:
Invalid face reference: nil [164 times]
The number "164" above is
On Feb 27, 2008, at 9:57 PM, Phil Jackson wrote:
Scott Otterson <[EMAIL PROTECTED]> writes:
[...]
+ expand matching pattern outwards until matching uniqueness is
assured across the whole file
This isn't foolproof as an identical line could be added later leaving
us with much the same probl
Scott Otterson <[EMAIL PROTECTED]> writes:
[...]
> + expand matching pattern outwards until matching uniqueness is
> assured across the whole file
This isn't foolproof as an identical line could be added later leaving
us with much the same problem.
> + store line number
This actually is alrea
Yes, starting with line numbers sounds like a good idea. So far, then,
the suggestion in its full glory is:
link storage
include punctuation in matching pattern
expand matching pattern outwards until matching uniqueness is
assured across the whole file
stor
Yeah, I guess that instead of saying it was a small bug, I should have
said that it's a bug of small consequence (for most users, but matters
to me, least).
The ambiguity problem you mention could be solved by matching more than
one line. To keep the string stored in the org link short,
org-
Forgot to mention this:
To reproduce the bug, after opening an org file, don't do anything
(don't even move the cursor), just press the return key. I use
"session.el", so when I open an org file, the cursor will go to the the
position of my last change in the buffer, and I can arrange the poi
Hi,
I have the following in my org-mode configuration:
(setq org-return-follows-link t)
Also, by default my org files are in overview mode (folded) when opened.
Usually, if my cursor is at the beginning of a heading, I can use the
return key to cycle the visibility of its subtree. However, th
Carsten Dominik <[EMAIL PROTECTED]> wrote:
> Hi Scott, this is not a small bug, but a problem that is really hard
> to solve.
> Supposed I used the exact line text to search, then you still have two
> lines in the buffer
> that would match.
>
> This is really about what strategy should be use
Tokuya Kameshima <[EMAIL PROTECTED]> writes:
> I wrote an emacs code, org-bookmark.el, which supports for orgmode
> links to Emacs bookmarks. You can store the links in the Bookmark
> List buffer by running M-x org-store-link.
Great, thanks.
> Not sure it's useful, but I regularly uses this boo
Hi Chris,
"Chris Randle" <[EMAIL PROTECTED]> writes:
> As I followed along, I spotted a couple of things:
>
> 1) Under "Your first formula", the first vmean formula you show is a
> column formula, whereas the text implies it should have been a field
> formula.
Well spotted, I fixed this.
> 2) I
Hi Tokuya,
this is nice, do you want me to add this to our distribution?
- Carsten
On Feb 27, 2008, at 4:39 PM, Tokuya Kameshima wrote:
Hi,
I wrote an emacs code, org-bookmark.el, which supports for orgmode
links to Emacs bookmarks. You can store the links in the Bookmark
List buffer by run
Maybe use SCHEDULED: instead of DEADLINE: ?
Wanrong Lin <[EMAIL PROTECTED]> writes:
> Changing appointment time stamp into deadline will work, but I just
> think conceptually it is kind of twisted, because "deadline" means you
> have to do it BEFORE the specified time, while "appointment" means
Hi,
I wrote an emacs code, org-bookmark.el, which supports for orgmode
links to Emacs bookmarks. You can store the links in the Bookmark
List buffer by running M-x org-store-link.
Not sure it's useful, but I regularly uses this bookmark links to
follow daily or weekly changing file links.
Thank
Changing appointment time stamp into deadline will work, but I just
think conceptually it is kind of twisted, because "deadline" means you
have to do it BEFORE the specified time, while "appointment" means you
have to do it at the specified time. Many calendar systems (like Google)
support ah
Thanks, I believe this is now fixes as well, please let me know if not.
- Carsten
On Feb 26, 2008, at 5:46 PM, Kondo Kenji wrote:
Thank you but I'm afraid there still exists one problem to fix.
When `org-publish-use-timestamps-flag' is t,
`C-c C-e P' or `M-x org-publish-current-project'
publ
This is a hard one - no fast fix.
- Carsten
On Feb 26, 2008, at 6:13 PM, Tim O'Callaghan wrote:
Hi.
There is some problem with tags and headings. I've had instances where
the tag has disappeared or merged into my heading.
Repeatable with Xemacs 21.4.19 i586-pc-win32, org 5.22a using this
f
Hi Scott, this is not a small bug, but a problem that is really hard
to solve.
Supposed I used the exact line text to search, then you still have two
lines in the buffer
that would match.
This is really about what strategy should be used to find a location
in a file that has possibly changed.
In Org-mode, by definition, Deadlines are the ones with ahead warnings.
Why don't you just turn the appointments where you need early
reminders into deadlines?
- Carsten
On Feb 26, 2008, at 11:01 PM, Wanrong Lin wrote:
Hi,
Currently we can set the number of days a deadline should be
noti
Hi Bastien,
Bastien Guerry wrote:
> Hi folks,
> i've made a small tutorial about the use of spreadsheet facilities in
> org-mode:
> http://www.legito.net/worg/org-tutorials/org-spreadsheet-intro.php
Thanks. It was very useful. I use tables and spreadsheets quite a lot,
but I still learnt a coup
40 matches
Mail list logo
