emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jonathan Arkell" <jonathana@criticalmass.com>
To: emacs-orgmode@gnu.org
Subject: A few new user questions, Custom agenda views, calendar in frame, and Hyperlinks on win32
Date: Wed, 19 Nov 2008 22:06:51 -0500	[thread overview]
Message-ID: <5146889A6969A24D82AFD05233CF024F012D518E@Haze.cmass.criticalmass.com> (raw)

Hi Everybody

I have some fairly simple new user questions, and I am hoping you guys can help me out.

I have a few custom agenda views that I would like to create, but I am having some issues.  My files are laid out in 1 file per project, and each file starts with a level 1 outline element tagged :project:.  (I do have other file types that are appropriately tagged).    I thought that if I wanted to list all TODOs in all my (appropriately tagged) project files, it would be as easy as setting up a custom agenda command.  The one I set up had a tags-todo type, with search “project” or “+project”, but I get … well… no results.  Ideally I’d like to have a couple of different lists, all project tagged files with TODO items and all project tagged files with WAITING items.  Can someone give me a hand?  (I’m not adverse to using setq in my .emacs, in fact, that might make things a little easier for me anyways)

Secondly, I am having an issue where my Calendar is popping up in a new frame all the time, either when scheduling an item or through remember.  I’d rather it pop up in a new window instead.  Is this possible?

Finally, I am having a problem with some external links, whenever I try to visit a file like \\AWindowsServer\path\to\file  I get the error message “eval: ShellExecute failed: The system cannot find the file specified. ^M”  Is it easy to fix this?  What is going on?

I am using org 6.10c, on Emacs W32 (Emacs v 22).

Thanks!

Jonathan Arkell
Sr. Web Developer
Inspired by Drum + Bass, Scheme, Kawaii
402 – 11 Avenue SE
Calgary, AB T2G 0Y4
t: 403.206.4377
www.criticalmass.com


The information contained in this message is confidential. It is intended to be read only by the individual or entity named above or their designee. If the reader of this message is not the intended recipient, you are hereby notified that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message.

             reply	other threads:[~2008-11-20  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  3:06 Jonathan Arkell [this message]
2008-11-20  3:39 ` A few new user questions, Custom agenda views, calendar in frame, and Hyperlinks on win32 Eddward DeVilla
2008-11-20  5:07 ` Matthew Lundin
2008-11-20  5:51 ` Nick Dokos
2008-11-20  6:42 ` Manish
2008-11-20 21:08 ` Mike Newman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5146889A6969A24D82AFD05233CF024F012D518E@Haze.cmass.criticalmass.com \
    --to=jonathana@criticalmass.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).