[Orgmode] [off-topic] emacs23 or emacs-snapshot-gtk (Ubuntu)
Hello fellow orgers, I have been using the emacs-snapshot package for a long time, since the era of Ubuntu 7.04, and it worked fine and I got all the latest versions of emacs with it. Now, I just installed 9.10 from scratch, and when I search for emacs on apt-cache, I get the following relevant packages: * emacs23 * emacs-snapshot-gtk The emacs-version for emacs23 returns: GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.2) of 2009-10-15 on yellow, modified by Debian For emacs-snapshot-gtk, I get: GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-27 on crested, modified by Debian Which one would be the most recent version (or better package to use)? Thanks in advance, Marcelo. ___ 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] [off-topic] emacs23 or emacs-snapshot-gtk (Ubuntu)
I have been using the emacs-snapshot package for a long time, since the era of Ubuntu 7.04, and it worked fine and I got all the latest versions of emacs with it. Now, I just installed 9.10 from scratch, and when I search for emacs on apt-cache, I get the following relevant packages: * emacs23 * emacs-snapshot-gtk The emacs-version for emacs23 returns: GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.2) of 2009-10-15 on yellow, modified by Debian For emacs-snapshot-gtk, I get: GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-27 on crested, modified by Debian Which one would be the most recent version (or better package to use)? I had some problems using emacs23 in Karmic. Several errors loading my .emacs and a non functional emacs-lisp menu. Using the ppa from https://launchpad.net/~ubuntu-elisp/+archive/ppa everything works as expected using the same .emacs. Ian. ___ 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] [off-topic] emacs23 or emacs-snapshot-gtk (Ubuntu)
Thanks for the reply. I had some problems using emacs23 in Karmic. Several errors loading my .emacs and a non functional emacs-lisp menu. Using the ppa from https://launchpad.net/~ubuntu-elisp/+archive/ppahttps://launchpad.net/%7Eubuntu-elisp/+archive/ppaeverything works as expected using the same .emacs. What is the difference between the emacs23 and emacs-snapshot-gtk packages? On Mon, Oct 26, 2009 at 12:19 PM, Ian Barton li...@manor-farm.org wrote: I have been using the emacs-snapshot package for a long time, since the era of Ubuntu 7.04, and it worked fine and I got all the latest versions of emacs with it. Now, I just installed 9.10 from scratch, and when I search for emacs on apt-cache, I get the following relevant packages: * emacs23 * emacs-snapshot-gtk The emacs-version for emacs23 returns: GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.2) of 2009-10-15 on yellow, modified by Debian For emacs-snapshot-gtk, I get: GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-27 on crested, modified by Debian Which one would be the most recent version (or better package to use)? I had some problems using emacs23 in Karmic. Several errors loading my .emacs and a non functional emacs-lisp menu. Using the ppa from https://launchpad.net/~ubuntu-elisp/+archive/ppahttps://launchpad.net/%7Eubuntu-elisp/+archive/ppaeverything works as expected using the same .emacs. Ian. ___ 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] [off-topic] emacs23 or emacs-snapshot-gtk (Ubuntu)
What is the difference between the emacs23 and emacs-snapshot-gtk packages? The snapshot is derived from the latest emacs in cvs. The emacs23 is the stable v23 release. The snapshot package will contain extra bugfixes, features and quite possibly some extra bugs:) Ian. ___ 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] [off-topic/GTD]Only Next Actions list to rule them all ?
Manish mailtomanish.sha...@gmail.com writes: On Wed, Oct 21, 2009 at 10:45 AM, Marcelo de Moraes Serpa wrote: Hello list, This is for the GTD orgers out there. I've taken the article written by Charles as a basis for my GTD implementation. In the end, it's all about what works for you, but I'd like to get some insights/opinions from you: For Next Actions, are you using a single list OR you organize them hierarchically under each project (in the projects list)? I started with the second one, putting each next action (TODO) item under its correspondent project, however, it quickly became too bloated, and a mix of projects, sub-projects and next-actions. Of course, org helps there with sparse trees and other functions to filter trees, but still, I found it was too complex, albeit more specific and I did felt I was more organized, even though I was getting lost. So, I just let go of my obsession about the perfect thing and decided to try a single Next Actions list, together with a Projects list. The next actions is a single list with all the actionable items from all the projects. I've lost the relationship between a next action item and a project, but I can do this easily by just looking at the action, having the system tell me is not that important. Usually, you define all actions for a project under the same hierarchy. You can decide how you want actions to be designated next (and projects to be designated project) -- using keywords or tags and have a custom agenda command collect the next actions for you from all agenda files in a single list. I use a single file which contains both next actions (NAs) and projects, with NAs living under the relevant project. NAs have TODO state and tags for the contexts. Well, that's not 100% true. My GTD file contains NAs and a more generic concept which I'm calling Categories, since a Category uses a CATEGORY property. Categories are just grouping items. Projects are a special kind of Category which a) have a TODO state (normal Categories do not) and b) tack a p_ onto the beginning of the CATEGORY label and c) have a project tag. Basically a project is a Category that you can finish and which can be immediately identified as a project with a query (because of the project tag). In this way, NAs always live under a Category (I have a Misc Category to catch NAs which don't seem to fit anywhere else), and some Categories are projects. I don't nest Categories into sub-Categories, but I think I could do it - projects are just Categories with some extra TODO state and tags, and heading level doesn't really enter into it. Similarly, NAs are TODO items which do NOT have the project tag. When I collect all my NAs into an agenda view, I immediately see the CATEGORY label in the first column and I can see which NAs belong to a project and which don't, since I tacked a p_ onto the Categories which represent projects. Also, my waiting list is defined as items in the WAITING state. I keep my someday list as a seperate file. -- Desmond Rivet Pain is weakness leaving the body. ___ 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] [off-topic/GTD]Only Next Actions list to rule them all ?
Hello list, This is for the GTD orgers out there. I've taken the article written by Charles as a basis for my GTD implementation. In the end, it's all about what works for you, but I'd like to get some insights/opinions from you: For Next Actions, are you using a single list OR you organize them hierarchically under each project (in the projects list)? I started with the second one, putting each next action (TODO) item under its correspondent project, however, it quickly became too bloated, and a mix of projects, sub-projects and next-actions. Of course, org helps there with sparse trees and other functions to filter trees, but still, I found it was too complex, albeit more specific and I did felt I was more organized, even though I was getting lost. So, I just let go of my obsession about the perfect thing and decided to try a single Next Actions list, together with a Projects list. The next actions is a single list with all the actionable items from all the projects. I've lost the relationship between a next action item and a project, but I can do this easily by just looking at the action, having the system tell me is not that important. So, basically, a bunch of projects and next actions, weekly review, collect-process-organize-review-do and that's all. Who knows, over time I might find that there's a better way... well, but Keeping It Simple is sometimes the best approach, even though org is so flexible that one might fall in the rabbit hole :) Thanks, Marcelo. ___ 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] [off-topic/GTD]Only Next Actions list to rule them all ?
On Wed, Oct 21, 2009 at 10:45 AM, Marcelo de Moraes Serpa wrote: Hello list, This is for the GTD orgers out there. I've taken the article written by Charles as a basis for my GTD implementation. In the end, it's all about what works for you, but I'd like to get some insights/opinions from you: For Next Actions, are you using a single list OR you organize them hierarchically under each project (in the projects list)? I started with the second one, putting each next action (TODO) item under its correspondent project, however, it quickly became too bloated, and a mix of projects, sub-projects and next-actions. Of course, org helps there with sparse trees and other functions to filter trees, but still, I found it was too complex, albeit more specific and I did felt I was more organized, even though I was getting lost. So, I just let go of my obsession about the perfect thing and decided to try a single Next Actions list, together with a Projects list. The next actions is a single list with all the actionable items from all the projects. I've lost the relationship between a next action item and a project, but I can do this easily by just looking at the action, having the system tell me is not that important. Usually, you define all actions for a project under the same hierarchy. You can decide how you want actions to be designated next (and projects to be designated project) -- using keywords or tags and have a custom agenda command collect the next actions for you from all agenda files in a single list. -- 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] Off
Hi all, now I'm off for real till the end of August. I couldn't handle some issues on time for today, but I know they will be sorted out. Also, I allowed myself to add a Make a donation button on my Org page - I'll remove this when I get enough $ for a new computer: http://lumiere.ens.fr/~guerry/bastien-org-mode.php Have fun! -- 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
[Orgmode] OFF-TOPIC - posting file snippets..
i realize that this is off topic, but i think it will help in the future as i continue to post.. i have seen lots of people posting file snippets to this list that are really well formatted.. something like: --[filename.txt]-- | contents of | |file | ---[end]--- well, not that ugly, but you get the idea.. my question is.. how are they doing that? thanks! ___ 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
