Re: [Orgmode] Dragging URLs to an org buffer
On Oct 3, 2006, at 19:27, Piotr Zielinski wrote: Hi, Here's a piece of elisp that allows you to drag URLs from a webbrowser (or other apps) to an org buffer. Great. Any suggestions welcome. The functionality is now part of org-mouse (I think it requires Emacs 22): http://www.cl.cam.ac.uk/~pz215/files/org-mouse.el I like the functionality, but I do find it too specialized to make this behavior the default. So I would weaken it, or enclose turning it on into a customization variable. The reasons why I find it too intrusive the way it is now are: - You enforce a colon for adding to the end of the line - you enforce a particular type of bullet. - when inserting in a empty line, the color switches to fixed-width quotation - people might want to use drag-and-drop to insert something into the text that happens to be a bullet item. Proposals: - Don't enforce the colon when inserting at the end of the line. - In the middle of a line, just insert there. - If the current line is a bullet or a headline, *and* if you drop *on* either the bullet or the headline stars, then make a new headline/bullet for the dragged text. Always make the bullet after the current line. (well, when inserting in front of a bullet, you could insert before the current...) - Respect the type of bullet: numbered, -, +, *. - Carsten ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Dragging URLs to an org buffer
On 04/10/06, Carsten Dominik [EMAIL PROTECTED] wrote: On Oct 3, 2006, at 19:27, Piotr Zielinski wrote: Here's a piece of elisp that allows you to drag URLs from a webbrowser (or other apps) to an org buffer. I like the functionality, but I do find it too specialized to make this behavior the default. So I would weaken it, or enclose turning it on into a customization variable. Yes, I completely agree with you, this was a hack that worked for me rather than something everybody could use. But I thought sharing it with others might be a good idea, even if only for useful feedback like yours. The only thing which I have a different opinion about is what to do when you drop a URL in the middle of the line. I believe this function should be assigned to normal paste (middle button). My goal was to make drag-and-drop useful for managing org-mode lists _without_ using a keyboard. For me this means: (i) an easy (keyboard-less) way of insterting a new list element before or after the current element, and (ii) inserting the URL into the current line, without the need of manual adjustment (adding spaces around, adding the colon, etc.). So while I agree that the behaviour must be customizable, I'd like a solution that satisfies these two criteria. Anyway, I'll do some modifications, and send the next version. The reasons why I find it too intrusive the way it is now are: - You enforce a colon for adding to the end of the line - you enforce a particular type of bullet. - when inserting in a empty line, the color switches to fixed-width quotation - people might want to use drag-and-drop to insert something into the text that happens to be a bullet item. Proposals: - Don't enforce the colon when inserting at the end of the line. - In the middle of a line, just insert there. - If the current line is a bullet or a headline, *and* if you drop *on* either the bullet or the headline stars, then make a new headline/bullet for the dragged text. Always make the bullet after the current line. (well, when inserting in front of a bullet, you could insert before the current...) - Respect the type of bullet: numbered, -, +, *. Piotr ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Dragging URLs to an org buffer
On Oct 4, 2006, at 17:30, Piotr Zielinski wrote: The only thing which I have a different opinion about is what to do when you drop a URL in the middle of the line. I believe this function should be assigned to normal paste (middle button). Yes, I forgot that I can use mouse-2 for this. Right. My goal was to make drag-and-drop useful for managing org-mode lists _without_ using a keyboard. For me this means: (i) an easy (keyboard-less) way of insterting a new list element before or after the current element, and (ii) inserting the URL into the current line, without the need of manual adjustment (adding spaces around, adding the colon, etc.). So while I agree that the behaviour must be customizable, I'd like a solution that satisfies these two criteria. Anyway, I'll do some modifications, and send the next version. OK, looking forward to it. - Carsten -- Carsten Dominik Sterrenkundig Instituut Anton Pannekoek Universiteit van Amsterdam Kruislaan 403 NL-1098SJ Amsterdam phone: +31 20 525 7477 ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Another GTD question.
I really like this discussion started by Alex. It has triggered for me a lot of thinking and clarity about how to use Org-mode for a GTD system. High time, because my current system basically is do whatever the closest person pointing a gun to your head is asking. Has kept me alive, if stressed :-). Charles Cave's [article/tutorial] gives a great overview over the basic structure of GTD and his views on implementing GTD with org-mode. Below are a few thoughts on how GTD elements can be represented in org-mode. 2 The (too?) many organizational elements of Org-mode ~ There are many ways to apply structure to your notes using Org-mode: - Categories (i.e. files) - Lists (outlines) - TODO keywords - TAGS and many of these can be used interchangeably. For example, if I am collecting the things I have to discuss with my colleagues Peter and Sarah, I could - use lists : * Agendas : ** Peter : *** item p1 : *** item p2 : ** Sarah : *** item s1 : *** item s2 - use TODO keywords : #+TYP_TODO: Peter Sarah : : * Project X : ** Peter item p1 : ** Sarah item s1 : * Project Y : ** Peter item p2 : ** Sarah item s2 - use TAGS : * Project X : ** item p1 :Peter: : ** item s1 :Sarah: : * Project Y : ** item p2 :Peter: : ** item s2 :Sarah: The same is true for contexts like [EMAIL PROTECTED]', [EMAIL PROTECTED]', [EMAIL PROTECTED]' etc as they are being used in GTD. You could make a list of things to be handled at your computer at home, or you could use tags for contexts. So what is the best way to approach these issues, what method should be preferred and why? I think his is the core of the present discussion. For me personally, the main advantage of Org-mode is that I can keep information relating to a project together in one place. This is best for many reasons, for example - things that belong together, stay together - easy review if a project is stuck So I would not generally make lists for a specific contexts or people. Lists for a specific person are unlikely as well. Most of the time I would use either TAGS or TODO keywords, also because the search functions for tags and TODO keywords are the most powerful ones in Org-mode. 3 CATEGORIES for broad splitting of the GTD system ~~ I am using separate files for things I need to do for HOME and for WORK. At work I use one big file for most things, but the biggest tasks/projects I split off and put them into a separate file. 4 TAGS versus TODO keywords versus Lists to implement GTD elements ~~ 4.1 Context === I think most of us agree that contexts (location and required tools for doing a task) is something best implemented with TAGS in the org-mode system. Tags like @home, @work, @phone, @computer, @mall can be defined and easily applied to any tasks that need that particular context. 4.2 The GTD lists as *status* of a task === Another important part of GTD terminology are different lists that contain tasks, for example NEXT ACTION, WAITING, or SOMEDAY/MAYBE. In the original GTD terminology these are called lists. When thinking about implementation in Org-mode, it occurred to me that these are better called /status of a task/ which is then used to make corresponding lists. Here is what I mean by status: - TODO: this is something that needs to be done, no further specification if this can be done now or not. - NEXT: this is something that can be done /now/, you have everything you need to start doing it. This is what /next actions/ are about. - WAITING: This item cannot be done now, because we are waiting for something. Somebody else needs to act, some material needs to arrive, etc. - SOMEDAY: means that you have not decided that this needs to be done. How should we go about implementing this structure in org-mode? 1. We could make physically separate lists for each task status. As I said, I don't like this idea and will not discuss it further. 2. We can use TODO keywords to implement these different states. Each time the state changes, we switch to a different TODO keyword. This is very easy from an Agenda view: `1 t', `2 t', `3 t' etc directly switch to the corresponding keyword. In the buffer, try `Shift-left/right' with the cursor on the keyword. 3. We can use TAGS to implement this structure. So each TODO item would have an additional tag, identifying the state of the task. - Advantage: you keep the simple on/off of a TODO item. - Disadvantage: When you mark an entry DONE, the NEXT tag (or whichever the current status is will stick around and put this item into your NEXT ACTION lists. Which of these two possibilities you choose
Re: [Orgmode] Another GTD question.
Hi, In relation to Carsten's email, I'd like to ask about possible integration of headings and plain lists. I remember that such integration was difficult because of the implementation of outline-mode, but I don't know the details. In case this is possible, here are a few reasons why I'd like it: 1. As opposed to headings, plain list items can consists of more than one line. On the other hand, they cannot be assigned tags or marked TODO. So, sometimes, one has to use one or the other. This is especially problematic, if you would like a TODO item below a multi-line plain list item. It would be great if the features of headings and plain lists could be, at least to some extent, combined. 2. Code duplication. At the moment, AFAIK, you need to write separate code for headings and plain lists. Also, some features exist for both but in different forms, for example, TODO/DONE for headings is essentially the same as [ ]/[X] for plain lists. I don't mind having different representation for the same concept as long as their share the same handling code. However, I feel that any attempt at integrating integrating headings and plain lists would require a significant rewrite. Carsten, could you please comment on the main difficulties of such integration? Thanks, Piotr ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org-log-done customization problem
Customization of org-log-done is lost when re-starting emacs. E.g., in my .emacs file, I have [relevant portion only] (custom-set-variables '(org-log-done (quote (done But, when I re-start emacs, describe-variable on org-log-done reports it simply as 't' and the new note-taking feature is disabled. If I re-set it to (done), the new feature works great (thanks Carsten, this is exactly what I was looking for). How do I get the customization to stick? Thanks, Dan ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
