searchcode | source code search engine

6+ results for 'bitbucket repo:arrayschism/Redmine Advanced Roadmap' (0 ms)

Not the results you expected?

Search Tips

If you have run a search that returned no results there are a few things to try. By default, searchcode prioritizes system survival (hey it's a free service!), and as such might do some load shedding, which can mean you don't see results you expect. You can do some things to help with this.

Filters

Filtering by language or source will cut down the number of results searchcode needs to look at. If you know a result for instance a term can be found in python code, specifying python re.compile lang:python via the lang:python syntax, or the sidebar filters.

You can also filter by filename database file:content where the filename must match at the start what you supply.

Add more terms or longer terms

Adding more search terms will now only improve relevance it will reduce the number of results that searchcode needs to inspect. So rather than searching for test consider trying unittest or test random.

Keep in mind searchcode uses AND logic. This means search will look for all of the terms you enter split by whitespace. So a search for *testing.T randomstring will look for documents which contain both *testing.T and randomstring in any order in a document, with a preference to displaying snippets where the terms are close together.

Literal search

Searchcode will literal search on anything, split by whitespace. This allows you to search for i++; if you like but it does mean that no advanced search query syntax is supported (for the moment anyway) outside of filters and exact match.

Exact match search

You can search for exact matches by enclosing them in quotes "class ScopSearch(unittest.TestCase):"

Smallest term size

The smallest term you can search for in searchcode is 3 characters long. This is because it uses a trigram index to search on. So a search for two characters, such as i+ will never return a result. However, i++ will. Note that while 2 character terms are not searched for if they are in a search with other longer terms it may be used for matching and displaying code snippets.

Case insensitive

Searchcode is case-insensitive. It actually lowercases everything it indexes, so it won't work as expected for some unicode points.

contents.rst (https://github.com/aka-katto/dandere2x.git) ReStructuredText · 212 lines

71 :doc:`Custom domains <custom_domains>`

73 * **Connecting with GitHub, BitBucket, or GitLab**:

74 :doc:`Connecting your account <connected-accounts>`

103

104

105 Advanced features of Read the Docs

106 ----------------------------------

107

108 Read the Docs offers many advanced features and options.

109 Learn more about these integrations and how you can get the most

110 out of your documentation and Read the Docs.

README.md (https://bitbucket.org/nexj/njsdoc) Markdown · 73 lines

6 Often this means things get specified twice, once in code and once in comments.

8 NJSDoc on the other hand evaluates the code using [modified Rhino](https://bitbucket.org/nexj/rhino-njsdoc) and stores the source code location of every assignment so it can calculate where

9 each value comes from and which JSDoc comment is most appropriate. NJSDoc uses the prototype chain to classify objects as classes (constructors)

10 and class members so it is compatible with many ad-hoc inheritance schemes.

12 # Roadmap #

14 * IDE integration to generate content assist for libraries - see: [https://bitbucket.org/nexj/webtools.jsdt.core](https://bitbucket.org/nexj/webtools.jsdt.core)

15 * Prettier output that looks more like traditional JSDoc

16 * Plugin system to support AMD and other module systems

68 # See Also #

70 * Modified Rhino required by NJSDoc: [https://bitbucket.org/nexj/rhino-njsdoc](https://bitbucket.org/nexj/rhino-njsdoc)

71 * Eclipse plugin exposing NJSDoc API: [https://bitbucket.org/nexj/njsdoc-build](https://bitbucket.org/nexj/njsdoc-build)

72 * Fork of the Eclipse Javascript editor JSDT using NJSDoc: [https://bitbucket.org/nexj/webtools.jsdt.core/src/njsdoc](https://bitbucket.org/nexj/webtools.jsdt.core/src/njsdoc)

admin.php (https://bitbucket.org/allanfreitas/bugitor) PHP · 88 lines

9 * /____/

10 * A Yii powered issue tracker

11 * http://bitbucket.org/jacmoe/bugitor/

12 *

64 </p>

66 <?php echo CHtml::link('Advanced Search','#',array('class'=>'search-button')); ?>

67 <div class="search-form" style="display:none">

68 <?php $this->renderPartial('_search',array(

79 'name',

80 'is_in_chlog',

81 'is_in_roadmap',

82 'position',

83 array(

init.rb (https://bitbucket.org/StrangeWill/redmine-advanced-roadmap) Ruby · 55 lines

16 end

18 ApplicationHelper.send(:include, AdvancedRoadmap::ApplicationHelperPatch)

19 Issue.send(:include, AdvancedRoadmap::IssuePatch)

21 Project.send(:include, AdvancedRoadmap::ProjectPatch)

22 ProjectsHelper.send(:include, AdvancedRoadmap::ProjectsHelperPatch)

23 Redmine::I18n.send(:include, AdvancedRoadmap::RedmineI18nPatch)

28 require_dependency "advanced_roadmap/view_hooks"

30 RAILS_DEFAULT_LOGGER.info "Advanced roadmap & milestones plugin for RedMine"

32 Redmine::Plugin.register :advanced_roadmap do

33 name "Advanced Roadmap"

34 url "https://bitbucket.org/StrangeWill/redmine-advanced-roadmap/"

35 author "Emilio GonzĂĄlez MontaĂąa, William Roush"

36 author_url "https://bitbucket.org/StrangeWill/redmine-advanced-roadmap/"

admin.php (https://bitbucket.org/zeroows/bugitor) PHP · 88 lines

9 * /____/

10 * A Yii powered issue tracker

11 * http://bitbucket.org/jacmoe/bugitor/

12 *

64 </p>

66 <?php echo CHtml::link('Advanced Search','#',array('class'=>'search-button')); ?>

67 <div class="search-form" style="display:none">

68 <?php $this->renderPartial('_search',array(

79 'name',

80 'is_in_chlog',

81 'is_in_roadmap',

82 'position',

83 array(

README.md (https://github.com/Uncommon/Xit.git) Markdown · 42 lines

17 * **Sidebar** showing branches, remotes, tags, submodules, and stashes.

18 * If you sign in with your TeamCity account, you can see build status for branches you have pushed.

19 * If you sign in with your Bitbucket Server account, you can see and act on pull requests.

20 * Support for more services, such as GitHub, is in the works.

21 * **History list** with a graph of commits and branches.

27 * Blame view has color coding to show lines that changed at the same time, and links back to the commit they came from.

29 # Roadmap

31 The plan is to have a concrete 1.0 milestone to provide a good foundation and firm direction moving forward. Version 1.0 will simply be a starting point covering basic usage, plus some fun extras like the beginnigs of online service integration.