From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: org-grep, and problems
Date: Tue, 15 Oct 2013 21:26:22 -0400 [thread overview]
Message-ID: <86txgit39d.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <20131015090643.GA6656@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Tue, 15 Oct 2013 11:06:43 +0200")
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> I can try debugging org-grep, but I don't know where I should start.
I would either step through org-grep (using C-u C-M-x first over any
line of the org-grep definition within org-grep.el, or add (message ...)
lines within the function before to later check the *Messages* buffer,
and after calling org-grep the normal way to trigger the trace, pay
special attention to the argument given to shell-command.
That command, repeated in a mere shell outside Emacs, should find hits
in your Org files. If not, I would play with that command to see how it
should have been written to be successful, then amend org-grep so it
generates the proper command.
If everything that should be found gets found, then I'd suspect the code
after shell-command which reformats the output, and step through it to
find where it does it wrong.
The code is small, so the bug does not have much room to hide :-).
François
next prev parent reply other threads:[~2013-10-16 1:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 15:50 org-grep, and problems François Pinard
2013-10-10 16:54 ` Suvayu Ali
2013-10-10 18:59 ` Suvayu Ali
2013-10-11 1:14 ` François Pinard
2013-10-11 7:43 ` Suvayu Ali
2013-10-14 23:50 ` François Pinard
2013-10-15 9:06 ` Suvayu Ali
2013-10-16 1:26 ` François Pinard [this message]
2013-10-13 21:43 ` R. Michael Weylandt <michael.weylandt@gmail.com>
2013-10-14 13:29 ` Suvayu Ali
2013-10-14 14:42 ` James Harkins
2013-10-14 18:19 ` Jonathan Leech-Pepin
2013-10-14 22:17 ` Alan L Tyree
2013-10-15 4:50 ` James Harkins
2013-10-16 1:15 ` François Pinard
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=86txgit39d.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--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).