Yes, it needs more consideration.
regards,
wenang.
On 10-09-08 23:38, Hans-Bernhard Bröker wrote:
> On 08.09.2010 15:04, Wengang Wang wrote:
> >On 10-09-07 22:39, Hans-Bernhard Bröker wrote:
> >>On 06.09.2010 14:26, wen.gang.wang@... wrote:
>
> [...]
>
> >Find functions calling this function: dlm_lock fs/ocfs2
>
> So what you're trying to say here is that you just use a blank
> inside the input pattern to split between the actual pattern and the
> path?
>
> Sorry, but that feels like a no-go. For starters, there's no way
> that can work with all queries --- some of them can have blanks as
> part of the pattern itself!
>
> >>How is this supposed to be used in line mode? Single-shot mode?
> >>Curses mode?
> >
> >Single-shot mode.
>
> You misunderstood my question. cscope has several modes of
> operation. Please see the man-page about options -L (single-shot
> mode) and -l (line mode) to understand the question.
>
> >the<subtree> doesn't affect future commands.
>
> How do you achieve that, if, e.g. the user uses cscope's built-in
> pattern history mechanism (Ctrl-b, Ctrl-f, Ctrl-y)?

Hi Hans,
On 10-09-07 22:39, Hans-Bernhard Bröker wrote:
> On 06.09.2010 14:26, wen.gang.wang@... wrote:
> >#please To/Cc me exlicitly since I'm not in the mailing list.
>
> Why not just subscribe?
Yes. It's a good idea :D
> >It looks like cscope shows result for the whole tree(where the database file is made)
> >for symbols.
>
> Of course it does! Searching for stuff in entire, big projects is
> the whole purpose of cscope's existence, after all.
Yes.
> >usage:
> >just add the subtree to the end of the cs command, say
> >:cs f c dlm_lock fs/ocfs2
>
> That's not really cscope usage --- it's usage of the VIM interface.
Yes, you are right.
For cscope usage, it's same too.
orig:
------------------------------------------------
Find functions calling this function: dlm_lock
File Function Line
0 lock_dlm.c gdlm_lock 165 error = dlm_lock(ls->ls_dlm, req, &gl->gl_lksb, lkf, gl->gl_strname,
1 stack_user.c user_dlm_lock 708 ret = dlm_lock(conn->cc_lockspace, mode, &lksb->lksb_fsdlm,
2 stackglue.c ocfs2_dlm_lock 252 return active_stack->sp_ops->dlm_lock(conn, mode, lksb, flags,
------------------------------------------------
patched:
------------------------------------------------
Find functions calling this function: dlm_lock fs/ocfs2
File Function Line
0 stack_user.c user_dlm_lock 708 ret = dlm_lock(conn->cc_lockspace, mode, &lksb->lksb_fsdlm,
1 stackglue.c ocfs2_dlm_lock 252 return active_stack->sp_ops->dlm_lock(conn, mode, lksb, flags,
------------------------------------------------
I have never touched emacs, so no example for it. I think it's the same.
> How is this supposed to be used in line mode? Single-shot mode?
> Curses mode?
Single-shot mode.
the <subtree> doesn't affect future commands.
>
> Is it supposed to work on all searches, or just a few of them? If
> the latter: which ones?
A few of them. Not for findregexp and findstring.
But if you like, it's easily to change to apply for all.
>
> >+extern char *path_filter;
>
> Ahem. There's no way am I accepting a patch to cscope that puts an
> 'extern' declaration into a *.c file.
Yes, I should move it to global.h.
The next drop of the patch will be posted when you have no more
questions..
regards,
wengang.

Never mind. I can still do :tags ;-)
On Fri, Sep 3, 2010 at 1:03 PM, Weiguang Shi <wgshizz@...> wrote:
> I was wondering if there is a command that can show me the places in
> chronological order that I visited while navigating through a large code base.
>
> In ctags with vim, I can do :tags, which will show the tag stack (history).
>
> Thanks.
> Wei
>

I was wondering if there is a command that can show me the places in
chronological order that I visited while navigating through a large code base.
In ctags with vim, I can do :tags, which will show the tag stack (history).
Thanks.
Wei