Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Global search doesn't search in XML files #1511

Closed
jch opened this issue Feb 4, 2014 · 12 comments
Closed

Global search doesn't search in XML files #1511

jch opened this issue Feb 4, 2014 · 12 comments

Comments

@jch
Copy link

jch commented Feb 4, 2014

I'm guessing the results are filtered out for some reason. Is there a way to configure this?

@kevinsawicki
Copy link
Contributor

Are these files in a git ignored folder?

@jch
Copy link
Author

jch commented Feb 4, 2014

Nope

@kevinsawicki
Copy link
Contributor

What repo are you seeing this on and can you include what you were searching for?

@jch
Copy link
Author

jch commented Feb 4, 2014

It's on the boxen repo, but my current working directory is /opt/boxen/shibboleth-idp/conf. Here's the directory tarball. http://cl.ly/0d3G10421q17 I was searching for Condition, which shows up in relying-party.xml. Here's a screenshot:

2014-02-04 at 1 08 pm

I'm on version 0.48.0

@kevinsawicki
Copy link
Contributor

And /opt/boxen/shibboleth-idp isn't a git repo?

@jch
Copy link
Author

jch commented Feb 4, 2014

Nope, no .git dir.

@kevinsawicki
Copy link
Contributor

And /opt/boxen isn't a git repo?

I'm asking because Atom thinks the files in your screenshot are ignored, they are greyed in the tree view, and the status bar has the ignored icon on it. That is why they aren't showing up in the search results, this is a preference though.

@jch
Copy link
Author

jch commented Feb 4, 2014

Ah, interesting. So /opt/boxen/repo is a git repository, but walking up /opt/boxen/shibboleth-idp doesn't show any git repos, even though it's reporting itself as a git repo.

jch@cupcake:~$ cd /opt/boxen/
jch@cupcake:/opt/boxen$ git st
fatal: Not a git repository (or any of the parent directories): .git
jch@cupcake:/opt/boxen$ cd repo
jch@cupcake:/opt/boxen/repo[master*]$ git st
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#   vendor/puppet/cache/github-puppet-saml-0.0.1.tar.gz
nothing added to commit but untracked files present (use "git add" to track)
jch@cupcake:/opt/boxen/repo[master*]$ cd ..
jch@cupcake:/opt/boxen$ cd shibboleth-idp
jch@cupcake:/opt/boxen/shibboleth-idp[master*]$ git st
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#   ../../../Library/Homebrew/boxen-monkeypatches.rb
#   ../../../Library/Homebrew/cmd/boxen-install.rb
#   ../../../Library/Homebrew/cmd/boxen-latest.rb
#   ../../../Library/Homebrew/cmd/boxen-upgrade.rb
nothing added to commit but untracked files present (use "git add" to track)
jch@cupcake:/opt/boxen/shibboleth-idp[master*]$

@jch jch closed this as completed Feb 6, 2014
@jch
Copy link
Author

jch commented Feb 6, 2014

@kevinsawicki Closing because the file is git ignored like you suggested. The difference is there's a versioned file at:

modules/projects/files/saml/shibboleth-idp/conf/attribute-resolver.xml

but also a corresponding generated file at:

shared/saml/files/shibboleth-idp/conf/attribute-resolver.xml

and of course, the "shared" dir is ignored. Sorry for the goose chase. 🐦

@kevinsawicki
Copy link
Contributor

No problem, glad we figured this out, here is the preference that controls this behavior, I always keep it off personally.

screen shot 2014-02-06 at 3 22 24 pm

@jch
Copy link
Author

jch commented Feb 7, 2014

Awesome! Thanks

On Thursday, February 6, 2014, Kevin Sawicki notifications@github.com
wrote:

No problem, glad we figured this out, here is the preference that controls
this behavior, I always keep it off personally.

[image: screen shot 2014-02-06 at 3 22 24 pm]https://f.cloud.github.com/assets/671378/2105095/a10e3878-8f85-11e3-8321-7843ae064d33.png

Reply to this email directly or view it on GitHubhttps://github.com//issues/1511#issuecomment-34386708
.

-Jerry
@whatcodecraves http://twitter.com/whatcodecraves
github http://github.com/jch

@lock
Copy link

lock bot commented Jan 27, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants