Re: [Orgmode] Easier customization of TODO keyword colors
On Sat, Sep 5, 2009 at 3:47 AM, Ryan C. Thompson wrote: > Bastien wrote: >> >> Interesting - would you like to add this in org-hacks? >> >> http://orgmode.org/worg/org-hacks.php >> >> If so, please send me your username on repo.or.cz (if you are not >> already a Worger...) >> >> Thank! >> > > I'm not on either, actually. I'm a relative newcomer to org-mode and elisp > hacking in general. But I'd love to see it on Worg. Added that for you. Should be online in an hour or so. http://orgmode.org/worg/org-contribute.php -- Manish ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: org-gnus-prefer-web-links
Matt Lundin writes: Hi Matt, > I set org-gnus-prefer-web-links to t so that org-remember stores links > to gmane nntp groups as web links rather than links to gnus. Recently > (within the last week or so) org-store-link no longer creates the web > link. > > Previously the stored link looked like this: > > http://mid.gmane.org/m24os8lym6.fsf%40fastmail.fm > > Now the link to the same article looks like this: > > gnus:nntp+news.gmane.org:gmane.emacs.orgmode#m24os8lym6@fastmail.fm > > Does this have something to do with the recent patches to org-gnus.el? With the current git master, I cannot reproduce the problem. Linking your message, I get: [[http://mid.gmane.org/m2y6p2wycn.fsf%40fastmail.fm][Email from Matt Lundin: org-gnus-prefer-web-links]] Bye, Tassilo ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.30d; Hide stars
On Sat, 5 Sep 2009 07:58:45 +0200 Carsten Dominik wrote: > For now I have reverted the offending commit. And I can confirm it works again. detlef > > - Carsten > > On Sep 5, 2009, at 7:42 AM, Carsten Dominik wrote: > > > Hi everyone, > > > > I am still unable to reproduce this. But I am running the latest > > cvs emacs. > > > > Two questions: > > > > - if you revert the critical commit, does the problem go away > > - if you use the latest Emacs, does the problem go away? > > > > Thanks. > > > > - Carsten > > > > > > > > > > > > On Sep 4, 2009, at 11:36 PM, Arne wrote: > > > >> Mark Elston comcast.net> writes: > >> > >>> > >>> Bernt Hansen wrote: > William Henney gmail.com> writes: > > > I can reproduce that too > >> > >> I have the same problem as well, fontification not working upon > >> startup, but > >> working for subsequent loads within the emacs session. Tried the > >> org-bug-submit > >> feature, but that did not get out of my laptop (laptop problem, not > >> an org > >> problem).I'm using the latest org-mode from the git repository > >> 6.30trans, > >> emacs 23.1.1, fedora 11. Happens for all "org" files regardless > >> of size or > >> header information. > >> > >> Same .emacs file and same org files work fine with old version of > >> org-mode on my > >> desktop. > >> > >> If you need more information to aid debugging this let me know. > >> > >> Arne > >> > versus uncompiled files. If I do a make clean removing all > the .elc > files then it works (for that commit) - but after make there it no > fontification when the file is originally loaded. The commit > before > this one works with and without compiling. > > >>> > >>> I saw this problem on one of my machines yesterday and today as > >>> well. I > >>> thought I had done something wrong. > >>> > After loading compiled sources and starting a minimal emacs on the > provided test.org I get (Org Fly Ind Font) on the status line > indicating > the active modes. > > If I C-c C-c on the #+STARTUP: line it changes to (Org Fly Font) > and > fontification returns. > > >>> > >>> The file I was seeing this with didn't have a #+... line so I found > >>> that if I closed the file and re-opened it then it fontified it just > >>> fine. > >>> > >>> Trying it on a different file with a #+TITLE: line I see I can do > >>> the > >>> C-cC-c thing and it works as well. > >>> > >>> However, I have a different machine that doesn't exhibit this > >>> behavior > >>> at all. Loading a .org file brings it up fontified properly the > >>> first > >>> time. I will have to look into the differences between the > >>> settings for > >>> these two machines. > >>> > >>> Mark > >>> > >>> ___ > >>> Emacs-orgmode mailing list > >>> Remember: use `Reply All' to send replies to the list. > >>> Emacs-orgmode gnu.org > >>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > >>> > >>> > >> > >> > >> > >> > >> > >> > >> ___ > >> Emacs-orgmode mailing list > >> Remember: use `Reply All' to send replies to the list. > >> Emacs-orgmode@gnu.org > >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > > > === > PLEASE NOTE NEW ADDRESS > === > prof.dr. Carsten Dominik domi...@uva.nl > Astronomical Institute 'Anton Pannekoek' > www.astro.uva.nl/~dominik > Faculty of Science, University of Amsterdam phone > +31-20-5257477/7491 > SCIENCE PARK 904, ROOM C4-106 fax +31-20-5257484 > 1098 XH Amsterdam, The Netherlands > mail: PO BOX 94249, 1090GE, Amsterdam > > > > > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: FILETAGS documentation clarification
Hi PT, On Sep 4, 2009, at 10:47 PM, PT wrote: Matt Lundin imapmail.org> writes: Any time you change one of the in-buffer settings line (e.g., #+FILETAGS), you need to refresh the buffer by hitting C-c C-c on the new or updated line. You don't have to reload the file. Here's the information in the manual: http://orgmode.org/manual/In_002dbuffer-settings.html Thanks, I haven't seen this page yet. Maybe every mention of an in-buffer keyword should be a link to the summary page you linked, so new users can quickly find this info by clicking on the keyword. Just a thought. I don't think this s possible. But in *many* places of the manual the fact that C-c C-c must be used to update in-buffer settings is mentioned. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.30trans (release_6.30d.5.gc125); make fails on org-ascii.el
Hi Daniel, Daniel Martins writes: > On the other hand: Shouldn't a simple `make' do everything needed > to succeed? > > On "How do I keep current with Org mode development?" > > http://orgmode.org/worg/org-faq.php# > keeping-current-with-Org-mode-development > > it is suggested the following commands > > git pull && make clean && make && make doc && make install > > I've put together with a command which updaes a bunch of svn > repositories from my students. > > The problem is: make clean before make FORCES recompiling the same > files again and not only the updated files! > > As org-mode is updated very often and the the compiling process is a > bit slow and always annoying > I decide to change the comand to > > git pull & && make && make install > > I dropped make doc because it seems that there is som problem with > texinfo files of these new version. > > The problem of omitting make clean isthat: if a file disappears its > compiled maybe will not disappear and cause problems. > > Therefore I repeat Sebastien request: > > Shouldn't a simple `make' do everything needed to succeed? I can't say anything definitive. All I know is that a simple "make && make install" usually works for me. But, as far as I understand it, omitting the "make clean" has the potential to cause problems, because org source files are occasionally renamed or made obsolete. So if you run into any problems after an install, you should run make clean. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.30trans (release_6.30d.5.gc125); make fails on org-ascii.el
Is it not possible to pu tsome directive in the Makefile in order to make check the presence of *.elc without corresponding *.el and deleting them BEFORE or simultaneously with recompilation process? It should improve the compilation process. Maybe it could be create a new directive such as make clean-install to keep make install with backward compatibility. Unfortunately I do not master makefile issues to do this by myself. The phrase "omitting the "make clean" has the potential to cause problems" may lead to "bogus bugs" here in the list. These king of bugs are really hard ti find. Daniel 2009/9/5 Matt Lundin > Hi Daniel, > > Daniel Martins writes: > > > On the other hand: Shouldn't a simple `make' do everything needed > > to succeed? > > > > On "How do I keep current with Org mode development?" > > > > http://orgmode.org/worg/org-faq.php# > > keeping-current-with-Org-mode-development > > > > it is suggested the following commands > > > > git pull && make clean && make && make doc && make install > > > > I've put together with a command which updaes a bunch of svn > > repositories from my students. > > > > The problem is: make clean before make FORCES recompiling the same > > files again and not only the updated files! > > > > As org-mode is updated very often and the the compiling process is a > > bit slow and always annoying > > I decide to change the comand to > > > > git pull & && make && make install > > > > I dropped make doc because it seems that there is som problem with > > texinfo files of these new version. > > > > The problem of omitting make clean isthat: if a file disappears its > > compiled maybe will not disappear and cause problems. > > > > Therefore I repeat Sebastien request: > > > > Shouldn't a simple `make' do everything needed to succeed? > > I can't say anything definitive. All I know is that a simple "make && > make install" usually works for me. > > But, as far as I understand it, omitting the "make clean" has the > potential to cause problems, because org source files are occasionally > renamed or made obsolete. So if you run into any problems after an > install, you should run make clean. > > Best, > Matt > > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] agenda-custom view with timegrid not showing inherited tags
I want to create a custom agenda view without all my :WEEKLY: tags appts to
focus on extraordinary appointmens on the week.
I could not do that directly because most :WEEKLY: tags were inherited.
I did a hack by eliminating the regexp "\\+1w>" common to all my weekly
todos but combinations with other inherited tags was not possible
How can I do this in a more elegante way?
Daniel
(setq org-agenda-custom-commands
'(
...
("l" "cLeaning Weekly"
agenda ""
((org-agenda-ndays 7) ;; agenda will start in week view
(org-agenda-repeating-timestamp-show-all t) ;; ensures that
repeating events appear on all relevant dates
(org-agenda-log-mode-items '(state))
(org-agenda-skip-function '(org-agenda-skip-entry-if
'scheduled 'deadline 'regexp "\\+1w>")
)
)
)
...
)
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-agenda-file-to-front (unbalanced parentheses))))
Hi Jai,
Jai Jeffryes writes:
> Thanks for looking at my message. So, here's what I came up with by following
> the instructions on the Feedback page you suggested.
Thanks!
> 1. Emacs version: GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600) of 2009-07-29 on
> SOFT-MJASON
> 2. Org version (it came with my Emacs install, I didn't do a separate
> installation of the mode):
> Org-mode version 6.21b
> 3. (Even though I'm writing to this email list, I was curious to try the
> command M-x org-submit-bug-report. That command is not defined in my Emacs.)
> 4. Here are the org-related commands in my init file. I found out how to set
> up
> my agenda files there instead of relying on the command that I'm demonstrating
> now.
>
> ;; Org mode
> (require 'org)
> (add-to-list 'auto-mode-alist '("\\.org$" . org-mode))
> (define-key global-map "\C-cl" 'org-store-link)
> (define-key global-map "\C-ca" 'org-agenda)
> (setq org-log-done t)
> (setq org-todo-keywords '("TODO" "WAITING" "DONE"))
> (setq org-agenda-include-diary t)
> (setq org-agenda-include-all-todo t)
> (setq org-agenda-files (file-expand-wildcards "J:/MyDocuments/GTD/org/*.org"))
Try to comment out the line above and use the custom interface to set
your agenda files. See if the error persists.
> 4. Creating a backtrace. The command C-u M-x org-reload RET does not exist on
> my Emacs.
> 5. I turned on the option to enter the debugger.
> 6. I visited a new file called sample.org. I didn't put it in the directory
> specified for agenda files in my init file (listed above). I wanted to add it
> interactively for this demo.
> 7. I saved that file.
> 8. I selected from the menu: Org --> File List for Agenda --> Add/Move Current
> File to Front of List
> 9. Here is the output from the *Backtrace* buffer.
>
> Debugger entered--Lisp error: (scan-error "Unbalanced parentheses" 17301
> 29246)
> scan-sexps(83 29245)
> forward-sexp(29245)
> custom-save-delete(custom-set-variables)
> custom-save-variables()
> custom-save-all()
> customize-save-variable(org-agenda-files ("j:/MyDocuments/GTD/sample.org"
> "j:
> /MyDocuments/GTD/org/GTDSteelWig.org" "j:/MyDocuments/GTD/org/
> SteelWigSomeday.org"))
> org-store-new-agenda-file-list(("j:/MyDocuments/GTD/sample.org" "j:/
> MyDocuments/GTD/org/GTDSteelWig.org" "j:/MyDocuments/GTD/org/
> SteelWigSomeday.org"))
> org-agenda-file-to-front(nil)
> call-interactively(org-agenda-file-to-front nil nil)
>
> I don't know Lisp, but I can count parentheses (or use Emacs to tell me what
> they match up with by backspacing over a right one and filling it back in
> again.) I don't see unbalanced parentheses in that output.
Maybe the unbalanced parentheses are in the custom-file, not in the
output. Is your custom-file eval'ing correctly?
Dynamically adding or removing files from the org-agenda-files variable
stores this variable in the custom file, even if you are setting this
variable outside the custom file. So, if you use C-c [ frequently, you
shouldn't set org-agenda-files outside of the custom-file.
Maybe the documentation should warn the user about this problem. I
don't see any simple solution...
--
Bastien
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Subversion for backups?
In light of this topic I've posted my process using mercurial and bitbucket from my Mac. I've added an hourly bash script to my daemons to push to my repo every hour. You can get all the details at http://www.20seven.org/journal/2009/09/backing-up-org-mode-files.html Cheers, *Greg Newman* http://20seven.org twitter: 20seven 2009/9/2 Sébastien Vauban > Hi Rainer, > > Rainer Stengele wrote: > > Sébastien Vauban schrieb: > >> Rainer Stengele wrote: > >>> > >>> I have a server in my office running the subversion server. > >>> > >>> Access is by port forwarding the subversion port via ssh - no matter > being > >>> under windows (putty) or under Linux (ssh). > >>> > >>> In this way I have my subversion server and repository virtually > "local", > >>> that is acces is always via svn://localhost/repository > >> > >> Just for my own understanding, why to you want your repository to appear > as > >> local? In case you wanna change the physical location of the SVN server, > >> and don't want to update any of the working copies? Something like that, > or > >> are there other major reasons for this setup? > > > > A reason is I use my notebook at home and at work. > > Having the "localhost" server solves the problem. > > I simply use different port forwarding scripts at home and at work. > > Thanks for the explanation. > > Seb > > -- > Sébastien Vauban > > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Stuck in a folded section when subtree is folded
If a header has some text content under it and the cursor is in the text then pressing TAB folds the content, but it doesn't change the cursor position, so the cursor is stuck in the folded part and, for example, beginning-of-line doesn't work, you can only get out from the folded part if you press cursor up/down Isn't it a bug? If I stand on a header which has only subheaders under it and I press TAB then the subtree is folded and the cursor is put back to the beginning of the header line apparently to avoid leaving the cursor in the folded part which is a nice gesture. Shouldn't the same happen when textual content is folded? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Release 6.30
Hi Carsten,
excellent, thanks a lot!
I now have have started with this regexp:
...
'(org-agenda-entry-text-exclude-regexps (quote ("^.*- State
\"DONE\".*\n" "^.*erzeugt:.*\n")))
...
which works except in cases like these:
...
- State "DONE" [2008-02-24 So 20:52]
- State "DONE" [2008-02-24 So 20:52]
erzeugt: [2008-01-12 Sa 21:40]
...
or
...
- State "DONE" [2008-02-24 So 20:51]
- State "DONE" [2008-02-24 So 20:51]
- State "DONE" [2008-02-24 So 20:51]
- State "DONE" [2008-02-24 So 20:51]
- State "DONE" [2008-02-24 So 20:50]
- State "DONE" [2008-02-24 So 20:50]
erzeugt: [2008-01-12 Sa 21:40]
...
The agenda weeds out alle lines except the last line "erzeugt ...".
Rainer
Carsten Dominik schrieb:
Hi Rainer,
On Sep 4, 2009, at 12:03 PM, Rainer Stengele wrote:
Hi Carsten,
Thanks for releasing all the new features!
It is amazing to see new features - which mostly make a lot of sense
for me - coming up all the time.
Carsten Dominik schrieb:
Hi,
I am releasing Org-mode version 6.30.
Enjoy!
- Carsten
Changes in Version 6.30
===
...
New mode to show some entry body text in the agenda
There is now a new agenda sub-mode called
`org-agenda-entry-text-mode'. It is toggled with the `E' key.
When active, all entries in the agenda will be accompanied by a
few lines from the outline entry. The amount of text can be
customized with the variable `org-agenda-entry-text-maxlines'.
this already avoids displaying drawer lines.
I also see lines like:
- State "DONE" from "WARTEN" [2009-08-04 Di 16:19]
- State "DONE" from "WARTEN" [2009-07-02 Do 09:43]
...
and in my remeber templates I always create lines like:
created: [2009-08-03 Mo 11:46]
with the creation date of the entry.
Would it be possible and make sense to set up a variable for a regexp
to exclude lines like the ones above from showing?
Yes, I agree this would make sense.
There is now a variable and a hook for this purpose:
org-agenda-entry-text-exclude-regexps
org-agenda-entry-text-cleanup-hook
HTH
- Carsten
rainer
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Org-mode version 6.30d; Hide stars
I had reverted to 6.30c when the problem cropped up. I too can confirm it is working again. I am using the latest cvs of emacs from a couple of days ago. Hope you figure it out. Mel On Fri, Sep 4, 2009 at 11:42 PM, Carsten Dominik wrote: > Hi everyone, > > I am still unable to reproduce this. But I am running the latest cvs > emacs. > > Two questions: > > - if you revert the critical commit, does the problem go away > - if you use the latest Emacs, does the problem go away? > > Thanks. > > - Carsten > > > > > > > On Sep 4, 2009, at 11:36 PM, Arne wrote: > > Mark Elston comcast.net> writes: >> >> >>> Bernt Hansen wrote: >>> William Henney gmail.com> writes: I can reproduce that too >>> >> I have the same problem as well, fontification not working upon startup, >> but >> working for subsequent loads within the emacs session. Tried the >> org-bug-submit >> feature, but that did not get out of my laptop (laptop problem, not an org >> problem).I'm using the latest org-mode from the git repository >> 6.30trans, >> emacs 23.1.1, fedora 11. Happens for all "org" files regardless of size >> or >> header information. >> >> Same .emacs file and same org files work fine with old version of org-mode >> on my >> desktop. >> >> If you need more information to aid debugging this let me know. >> >> Arne >> >> versus uncompiled files. If I do a make clean removing all the .elc files then it works (for that commit) - but after make there it no fontification when the file is originally loaded. The commit before this one works with and without compiling. >>> I saw this problem on one of my machines yesterday and today as well. I >>> thought I had done something wrong. >>> >>> After loading compiled sources and starting a minimal emacs on the provided test.org I get (Org Fly Ind Font) on the status line indicating the active modes. If I C-c C-c on the #+STARTUP: line it changes to (Org Fly Font) and fontification returns. >>> The file I was seeing this with didn't have a #+... line so I found >>> that if I closed the file and re-opened it then it fontified it just >>> fine. >>> >>> Trying it on a different file with a #+TITLE: line I see I can do the >>> C-cC-c thing and it works as well. >>> >>> However, I have a different machine that doesn't exhibit this behavior >>> at all. Loading a .org file brings it up fontified properly the first >>> time. I will have to look into the differences between the settings for >>> these two machines. >>> >>> Mark >>> >>> ___ >>> Emacs-orgmode mailing list >>> Remember: use `Reply All' to send replies to the list. >>> Emacs-orgmode gnu.org >>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >>> >>> >>> >> >> >> >> >> >> ___ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> > > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] PATCH: prevent filling of #+ lines
This patch prevents fill-paragraph from acting on lines that start with #+ (optionally preceded by spaces or tabs). For example, at the moment if you have #+HTML: some html here Long line of normal text here and it goes on and on and on and on and on and on and on And then issue fill-paragraph (M-q) on the "Long line of normal text..." line, I end up with #+HTML: some html here Long line of normal text here and it goes on and on and on and on and on and on and on With this patch I get #+HTML: some html here Long line of normal text here and it goes on and on and on and on and on and on and on Same problem for paragraphs below source code blocks, etc. Dan --8<---cut here---start->8--- diff --git a/lisp/org.el b/lisp/org.el index 87b044b..e943fa5 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -16312,7 +16312,7 @@ which make use of the date at the cursor." ;; text in a line directly attached to a headline would otherwise ;; fill the headline as well. (org-set-local 'comment-start-skip "^#+[ \t]*") - (org-set-local 'paragraph-separate "\f\\|\\*+ \\|[ ]*$\\|[ \t]*[:|]") + (org-set-local 'paragraph-separate "\f\\|\\*+ \\|[ ]*$\\|[ \t]*[:|]\\|[ \t]*#\\+") ;; The paragraph starter includes hand-formatted lists. (org-set-local 'paragraph-start @@ -16320,6 +16320,7 @@ which make use of the date at the cursor." "\f" "\\|" "[ ]*$" "\\|" "\\*+ " "\\|" +"[ \t]*#\\+" "\\|" "[ \t]*\\([-+*][ \t]+\\|[0-9]+[.)][ \t]+\\)" "\\|" "[ \t]*[:|]" "\\|" "\\$\\$" "\\|" --8<---cut here---end--->8--- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: PATCH: proposed improvements to org-src-mode
Carsten Dominik writes: > Hi Dan, > > OK, I have now applied the patch. If you don't mind, could > you please double-check the commit? [Re.: commit 4b6988bf36cb458c9d113ee4332e016990c1eb04 ] Thanks Carsten, I looked over the commit and it looked good. However after using it a bit over the last week I have discovered two bugs and a code issue. These follow below, together with proposed patches. There are 3 separate patches. Just in case you want to accept all 3 of them, I've created a single patch against current git right at the bottom of the email. But first, there are a couple of aesthetic choices being made here that others might have better ideas for than the ones I've come up with so far. Firstly, how should we name edit buffers? At the moment we're using my proposal of (actually I just added spaces inside the square brackets) (concat "*Org Src " org-buffer-name "[ " lang " ]*") e.g. "*Org Src testing.org[ python ]*" Secondly, how shall we name edit buffers for Fixed Width / ASCII drawing regions? The patch below uses (concat "*Org Src " org-buffer-name "[ " "Fixed Width" " ]*") e.g. "*Org Src testing.org[ Fixed Width ]*" (Maybe "Literal" would be better? Neither seems perfect.) Now for the bugs & patches. * Bug 1: C-x s switches active buffer 1. open two edit buffers simultaneously and modify them 2. now issue C-x s in one of the edit buffers 3. when it comes to saving the second edit buffer, it will steal focus. Would an appropriate solution be to wrap the body of org-edit-src-save in a save-window-excursion, as in this patch? I've tried it quickly and it seems to have the desired effect. --8<---cut here---start->8--- diff --git a/lisp/org-src.el b/lisp/org-src.el index fbf395f..df09f39 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -474,14 +474,15 @@ the language, a switch telling of the content should be in a single line." (defun org-edit-src-save () "Save parent buffer with current state source-code buffer." (interactive) - (let ((p (point)) (m (mark)) msg) -(org-edit-src-exit) -(save-buffer) -(setq msg (current-message)) -(org-edit-src-code) -(push-mark m 'nomessage) -(goto-char (min p (point-max))) -(message (or msg "" + (save-window-excursion +(let ((p (point)) (m (mark)) msg) + (org-edit-src-exit) + (save-buffer) + (setq msg (current-message)) + (org-edit-src-code) + (push-mark m 'nomessage) + (goto-char (min p (point-max))) + (message (or msg "") --8<---cut here---end--->8--- * Bug 2: org-edit-src-find-buffer fails to find buffer - Use C-c ' to switch to an edit buffer and make a modification - Return to the org buffer without killing edit buffer - Try C-c ' on the same code block - You are now in a new edit buffer instead of returning to the original one! This is because it had not been updated to reflect the new edit buffer naming scheme. I propose that we ensure consistency by creating a new function org-src-construct-edit-buffer-name which takes the parent buffer name and the language and generates the edit buffer name, as in this patch. --8<---cut here---start->8--- diff --git a/lisp/org-src.el b/lisp/org-src.el index df09f39..b0932c1 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -185,7 +185,8 @@ the edited version." (org-delete-overlay org-edit-src-overlay))) (kill-buffer buffer)) (setq buffer (generate-new-buffer - (concat "*Org Src " (file-name-nondirectory buffer-file-name) "[" lang "]*"))) + (org-src-construct-edit-buffer-name + (file-name-nondirectory buffer-file-name) lang))) (setq ovl (org-make-overlay beg end)) (org-overlay-put ovl 'face 'secondary-selection) (org-overlay-put ovl 'edit-buffer buffer) @@ -231,13 +232,17 @@ the edited version." (if buf (switch-to-buffer buf) (error "Something is wrong here" +(defun org-src-construct-edit-buffer-name (org-buffer-name lang) + "Construct the buffer name for a source editing buffer" + (concat "*Org Src " org-buffer-name "[ " lang " ]*")) + (defun org-edit-src-find-buffer (beg end) "Find a source editing buffer that is already editing the region BEG to END." (catch 'exit (mapc (lambda (b) (with-current-buffer b -(if (and (string-match "\\`*Org Edit " (buffer-name)) +(if (and (string-match "\\`*Org Src " (buffer-name)) (local-variable-p 'org-edit-src-beg-marker (current-buffer)) (local-variable-p 'org-edit-src-end-marker (current-buffer)) (equal beg org-edit-src-beg-marker) @@ -289,7 +294,9 @@ the fragment in the Org-mode buffer." (if (boundp 'org-edit-src-overlay) (org-delete-overlay org-edit-src-overlay))) (kill-buf
RE: [Orgmode] org-agenda-file-to-front (unbalanced parentheses))))
Bastien,
Thanks for looking at my message. So, here's what I came up with by following
the instructions on the Feedback page you suggested.
1. Emacs version: GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600) of 2009-07-29 on
SOFT-MJASON2. Org version (it came with my Emacs install, I didn't do a
separate installation of the mode):Org-mode version 6.21b
3. (Even though I'm writing to this email list, I was curious to try the
command M-x org-submit-bug-report. That command is not defined in my Emacs.)4.
Here are the org-related commands in my init file. I found out how to set up my
agenda files there instead of relying on the command that I'm demonstrating now.
;; Org mode(require 'org)(add-to-list 'auto-mode-alist '("\\.org$" .
org-mode))(define-key global-map "\C-cl" 'org-store-link)(define-key global-map
"\C-ca" 'org-agenda)(setq org-log-done t)(setq org-todo-keywords '("TODO"
"WAITING" "DONE"))(setq org-agenda-include-diary t)
(setq org-agenda-include-all-todo t) (setq
org-agenda-files (file-expand-wildcards "J:/MyDocuments/GTD/org/*.org"))
4. Creating a backtrace. The command C-u M-x org-reload RET does not exist on
my Emacs.
5. I turned on the option to enter the debugger.6. I visited a new file called
sample.org. I didn't put it in the directory specified for agenda files in my
init file (listed above). I wanted to add it interactively for this demo.
7. I saved that file.8. I selected from the menu: Org --> File List for Agenda
--> Add/Move Current File to Front of List9. Here is the output from the
*Backtrace* buffer.
Debugger entered--Lisp error: (scan-error "Unbalanced parentheses" 17301 29246)
scan-sexps(83 29245) forward-sexp(29245)
custom-save-delete(custom-set-variables) custom-save-variables()
custom-save-all() customize-save-variable(org-agenda-files
("j:/MyDocuments/GTD/sample.org" "j:/MyDocuments/GTD/org/GTDSteelWig.org"
"j:/MyDocuments/GTD/org/SteelWigSomeday.org"))
org-store-new-agenda-file-list(("j:/MyDocuments/GTD/sample.org"
"j:/MyDocuments/GTD/org/GTDSteelWig.org"
"j:/MyDocuments/GTD/org/SteelWigSomeday.org")) org-agenda-file-to-front(nil)
call-interactively(org-agenda-file-to-front nil nil)
I don't know Lisp, but I can count parentheses (or use Emacs to tell me what
they match up with by backspacing over a right one and filling it back in
again.) I don't see unbalanced parentheses in that output. I did try stepping
through the code in the debugger once as an experiment. It went on and on and I
finally held down the step key and let it do what seemed like hundreds of
steps. It never errored out. I finally used whatever command it is that steps
out. Guess what? That time, it added the file to the agenda file list.
I'm trying to be complete about what I did, although I'm just experimenting.
Did any of that clarify anything?
Thanks for your help.
Jai
> From: bastiengue...@googlemail.com
> To: jaijeff...@hotmail.com
> CC: emacs-orgmode@gnu.org
> Subject: Re: [Orgmode] org-agenda-file-to-front (unbalanced parentheses
> Date: Fri, 4 Sep 2009 16:16:28 +0800
>
> Hi Jai,
>
> I cannot reproduce this error. Please send a more detailed backtrace by
> following the instructions here:
>
> http://orgmode.org/manual/Feedback.html
>
> Thanks,
>
> Jai Jeffryes writes:
>
> > I get a scan error when I try to add my current ORG file to the list of
> > agenda
> > files.
> >
> > I'm using Emacs 23.1.1 on Windows, so it has the Org mode built in.
> >
> > I create a new .ORG file, add some text, and save it.
> >
> > Then I type C-c [
> >
> > and I get this error.
> >
> > Scan error: "Unbalanced parentheses", 17495, 29440
> >
> > Any ideas?
> >
> > The same thing happens if I use the menu:
> >
> > Org --> File list for agenda --> Add/Move current file to front of list
> >
> > Or the full command: org-agenda-file-to-front
> >
> > I tried running the debugger, but that part of Emacs I've never learned. I
> > haven't done my own Lisp programming. I'd provide some more info if someone
> > wanted to prompt me on the next thing to try!
> >
> > Jai Jeffryes
> > NYC
> >
> > ━━━
> > Windows Live: Keep your friends up to date with what you do online. Find out
> > more.
> >
> > ___
> > Emacs-orgmode mailing list
> > Remember: use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> --
> Bastien
_
Windows Live: Make it easier for your friends to see what you’re up to on
Facebook.
http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_facebook:082009___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http:/
[Orgmode] Org-mode Makefile: make clean needed? make doc error?
Keeping update with org-mode has giving me some headaches with the Makefile These headaches come from my lack of knowledge probably. First is the necessity or not of make clean before make forcing to recompile ALL *.el even those unchanged. On slow computers, maybe this is a problem. The other problem is make doc I am always getting the Fatal Error below dan...@martins:~/emacs-lisp/org-mode$ make doc (cd doc; texi2pdf org.texi) This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) %&-line parsing enabled. entering extended mode (./txiversion.tex LaTeX2e <2005/12/01> Babel and hyphenation patterns for english, usenglishmax, dumylang, noh yphenation, portuguese, loaded. (/home/daniel/emacs-lisp/org-mode/doc/texinfo.tex Loading texinfo [version 2003-02-03.16]: Basics, pdf, (/usr/share/texmf-texlive/tex/plain/misc/pdfcolor.tex) fonts, ! Undefined control sequence. \resetmathfonts ...font 2=\tensy \textfont \itfam =\tenit \textfont \slfam =... l.1414 \textfonts ? ! Emergency stop. \resetmathfonts ...font 2=\tensy \textfont \itfam =\tenit \textfont \slfam =... l.1414 \textfonts ! ==> Fatal error occurred, no output PDF file produced! Transcript written on txiversion.log. /usr/bin/texi2dvi: texinfo.tex appears to be broken, quitting. make: ** [doc/org.pdf] Erro 1 ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: agenda-custom view with timegrid not showing inherited tags
PROBLEM SOLVED
I have found the solution hidden in the list:
(org-agenda-filter-preset '("-WEEKLY"))
2009/9/5 Daniel Martins
> I want to create a custom agenda view without all my :WEEKLY: tags appts to
> focus on extraordinary appointmens on the week.
>
> I could not do that directly because most :WEEKLY: tags were inherited.
>
>
> I did a hack by eliminating the regexp "\\+1w>" common to all my weekly
> todos but combinations with other inherited tags was not possible
>
> How can I do this in a more elegante way?
>
> Daniel
>
> (setq org-agenda-custom-commands
> '(
> ...
> ("l" "cLeaning Weekly"
> agenda ""
> ((org-agenda-ndays 7) ;; agenda will start in week view
> (org-agenda-repeating-timestamp-show-all t) ;; ensures that
> repeating events appear on all relevant dates
> (org-agenda-log-mode-items '(state))
> (org-agenda-skip-function '(org-agenda-skip-entry-if
> 'scheduled 'deadline 'regexp "\\+1w>")
>)
> )
> )
> ...
> )
>
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
