From: John Hendy <jw.hendy@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Using org-mode as a personal help desk tool
Date: Mon, 20 Jun 2016 11:44:53 -0500 [thread overview]
Message-ID: <CA+M2ft9TNeJ_NeRgjcgyWiCLs4yBWy5WGpFjMn14OQFHb0bsdA@mail.gmail.com> (raw)
In-Reply-To: <871t3sne87.fsf@ericabrahamsen.net>
On Mon, Jun 20, 2016 at 9:10 AM, Eric Abrahamsen
<eric@ericabrahamsen.net> wrote:
> Roland Everaert <reveatwork@gmail.com> writes:
>
>> Hi,
>>
>> I am working as a sysadmin, In the organization, we use 2 tools to
>> keep track of requests sent by the customers/users. As you can expect,
>> those tools are not meant to be used to track all the gritty details
>> of a sysadmin's job.
[snip]
>> 4. Being able to search for a particular aspect or getting a list of
>> them and access it.
>
> I actually don't think there's any built-in way of searching files in an
> org-attach directory.
>
I wasn't familiar with org-attach. Seeing the gist of it, and with dir
creation handled, what about updating org-agenda-files with the new
files (script or something), or just defining a top level dir to
search:
- http://stackoverflow.com/questions/11384516/how-to-make-all-org-files-under-a-folder-added-in-agenda-list-automatically
If this could be done, a file tag matching the directory name could
perhaps be used. Or just match the file name to something related to
the customer/user (in my standard agenda search you just see the name
of the file and the tags, not the parent dir name).
Just an idea.
John
next prev parent reply other threads:[~2016-06-20 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:45 Using org-mode as a personal help desk tool Roland Everaert
2016-06-20 14:10 ` Eric Abrahamsen
2016-06-20 16:44 ` John Hendy [this message]
2016-06-22 12:26 ` Roland Everaert
2016-06-28 18:09 ` darcamo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+M2ft9TNeJ_NeRgjcgyWiCLs4yBWy5WGpFjMn14OQFHb0bsdA@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.