Re: Why I don't like DXR

I second the sentiment: it's clear that DXR needs a real manual. I've got the start of one at https://dxr.readthedocs.io/en/latest/use.html. So if you want to file PRs against https://github.com/mozilla/dxr/blob/master/docs/source/use.rst, we can grow that into a proper manual, import it into

Re: Why I don't like DXR

> I wanted to find usage of a member called "io_pending". DXR is happy to search for identifiers (id:whatever). The problem is that all the uses of io_pending are #ifdef'd out when compiling for Linux, which is the platform we use to run the indexing job for moz-central. A clue is that there's

Re: DXR: How to search for a file that has since been removed from the tree?

> Can DXR help me track this down? And the short answer: no, DXR is for only one point in time so far. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: DXR: How to encourage people to link to perma-links instead of plain ones?

> When you click a link to a particular line in dxr, that would normally > navigate from https://dxr/footo https://dxr/foo#lineno. Instead, have it > navigate to https://dxr/rev/foo#lineno. If done as a straight navigation, > it's annoying, because it reloads the page. So instead, do it as a

Re: MXR permanently offline, please transition to DXR

> Is this also the case for non-C++ code in the tree? The non-C++ code in a C++ project updates atomically with the C++ code in order to show a coherent view (and search DB) of the project. Projects that have no build step, like webtools, obviously don't run into such build issues.

Re: MXR permanently offline, please transition to DXR

> Simple question: How often is DXR refreshed from, say, mozilla-central. Every 6 hours. However, if it doesn't build successfully, it doesn't update (since DXR uses information exfiltrated from the compiler to give more accurate search results than MXR). That's what's happening now:

Re: MXR permanently offline, please transition to DXR

> All I need now is an open search engine for c-c to plug into Firefox search > box. ;) There's actually a bug open about this already, with some hints on how to get started: https://bugzilla.mozilla.org/show_bug.cgi?id=813521 ___ dev-platform mailing

Re: DXR problem?

I get a underline on hover, plus my cursor changes to the "context-menu" one. What happens for you? > On Jul 6, 2016, at 8:40 , Richard Z wrote: > > works ... slightly unintuitive behaviour as howering over the symbols doesn't > show > any indication it is clickable.

Re: DXR problem?

> tried dxr as replacement for lxr yesterday and today and it > does not seem to work for me. > Whatever I type into the searchbox the results is just an > empty "This page was generated by DXR ."? We are about to squash a JS bug that affects older FFs and Safari:

Re: MXR permanently offline, please transition to DXR

Hi, Kendall. As a pain mitigation strategy for MXR URLs embedded immutably in Bugzilla and in people's Awesomebar histories, can we redirect MXR requests as Dão suggests? Some won't work, but many will, and those people will be less sad. > On Jun 30, 2016, at 10:20 , Dão Gottwald

Re: MXR permanently offline, please transition to DXR

Thanks for pointing this out! We've increased the contrast in https://github.com/mozilla/dxr/commit/a0b7afeb82bc9903d8c80494fb487b93ef280b70. Do feel free to file bugs in the future. Cheers, Erik > On Jun 25, 2016, at 0:45 , Philip Chee wrote: > > MXR uses black text

Re: Proposing preferring Clang over GCC for developer buidls

An additional bonus is that our ability to build with clang would break less often. That's been the cause of more than a few scuttled DXR indexing jobs. > On Mar 2, 2016, at 17:50 , Gregory Szorc wrote: > > switching developer builds to prefer > Clang over GCC

DXR 2.0 And Beyond: A Whistler Session

: * Cross-project search * Arbitrary boolean queries * Search by color * JS support * IDL support * Useful visualizations Add it to your Whistler schedule: http://sched.co/3gWR Cheers, Erik Rose DXR Project Lead ___ dev-platform mailing list dev-platform

Re: DXR 2.0 staged. Feedback please!

I am wondering, how close are we to be able to index IDL/WebIDL files, and navigate through JS and C++ callers and implementations of those attributes/methods? That is currently the biggest reason why I have to use MXR from time to time, and it would be nice to see DXR growing support for

Re: DXR 2.0 staged. Feedback please!

It looks like finding of overrides of virtual methods is missing from DXR 2.0. Is this intentional? Hmm, no. The tests seem to pass (https://github.com/mozilla/dxr/blob/es/dxr/plugins/clang/tests/test_overrides.py). Where are you seeing it? ___

Re: DXR 2.0 staged. Feedback please!

Is indexing all the various release branches a blocker? For decommissioning MXR it is. We'll have all the trees MXR does before we think about turning it off. ___ dev-platform mailing list dev-platform@lists.mozilla.org

DXR 2.0 staged. Feedback please!

: better surfacing of symbols without having to know their type ahead of time, faceted drill-down, context for search results, and permalinks (our last major blocker to decommissioning MXR). Thanks for helping test it out! Erik Rose DXR Lead ___ dev-platform

DXR Session Wednesday

Dear DXR contributors and users, I'm pleased to announce a session Wednesday detailing the last 6 months of DXR development and its future roadmap. Time permitting, it might then turn into a planning/working session. DXR is entering an exciting time. We are finishing up what amounts to a minor

DXR Intern Presentation

Marcell has been my intern on the DXR project these past months, and it's been a privilege to work with him. From JavaScript analysis to Elasticsearch to writing Haskell in Python, he's cut an impressive swath through the codebase, and you can expect to see a lot of his handiwork deployed in

Re: Are you interested in doing dynamic analysis of JS code?

query results more useful. Being able to find where undefineds or NaNs pop out of running code would make it easier to spotlight ones which are spurious. We'd love to have the hooks! -- Erik Rose DXR Lead ___ dev-platform mailing list dev-platform

Multi-line highlighting landed

Thanks to contributor Jamon Camisso, multi-line highlighting has just landed in DXR. Now you can do things like this... http://dxr.mozilla.org/mozilla-central/source/CLOBBER#10-15,18-22,4-5 ...by pressing buttons like this: http://dxr.readthedocs.org/en/latest/code-highlighter.html

Re: DXR gets multi-line highlighting

Note that for this, analysis of the tip of each of -release, -beta, -aurora and -esr* would be enough. That's significantly more than just doing -central, but it's also significantly less than doing every single revision. That is planned! ___

Re: DXR gets multi-line highlighting

Whee, I get to be a wet blanket! We don't even have any request-writable storage at the moment. SQLite is horrible with write concurrency (and is on an NFS share, to make matters worse), and straight NFS-based writing (sans SQL) would have to be guarded with locks. Even if we solved those

Re: DXR gets multi-line highlighting

On Mar 14, 2014, at 9:45 , Mats Palmgren m...@mozilla.com wrote: Would it possible to also support multiple ranges? You bet. In fact, yours wasn't the only request along those lines. ___ dev-platform mailing list dev-platform@lists.mozilla.org

DXR gets multi-line highlighting

A lot of you have asked for the ability to select and share ranges within source files. Now, thanks to contributor Jamon Carmisso, you can: http://dxr.mozilla.org/mozilla-central/source/content/media/AbstractMediaDecoder.h#7-13 As on GitHub, just click one line number and shift-click another.

Re: DXR now indexing comm-central

One thing I did notice in passing is that DXR doesn't provide a count of results like MXR does. It's on our roadmap (https://wiki.mozilla.org/DXR_Roadmap#UI.2FUX) but a pretty low priority atm. What's your use case, in case we should bump it up? Also I tried looking up the callers of a

DXR now indexing comm-central

We've just added comm-central to DXR! You can find it at http://dxr.mozilla.org/comm-central/source/ or through the new Switch Tree menu. The menu knows some tricks: it tries hard to preserve things like your browsing position and your search query while moving from tree to tree, so you can

Re: DXR UI refresh is live!

Why are you double spacing the output and then fixing it by hard-coding .7 line spacing for the source and 1.4 for the line numbers? That was weird. Nobody knew why. Fixed now: https://github.com/mozilla/dxr/commit/16784204ce30c428cc3e325d7f5ccd225346bfdf. This also makes copying and pasting

Re: DXR UI refresh is live!

Hi, Reed. Rest assured, many of your wishes are planned for the future. But when you have a big project, you've got to pick some things. Last week's release was an important milestone: it was the minimal feature set that would yield a cohesive experience under a UI new design. The new design

Re: DXR UI refresh is live!

that's pretty, but where did the list of classes class members go when viewing files like http://dxr.mozilla.org/mozilla-central/source/modules/libjar/nsZipArchive.cpp I believe this is fixed now, a casualty of a needless use of JS, which is now gone. If you still see this behavior, please

Re: DXR UI refresh is live!

I notice the click here to view all search results link is at the top of the code listing now, instead of being with the search bar. That means it'll be invisible most of the time. First, let me say that we're still moving error messages around. We'll probably end up with something like this

Re: DXR UI refresh is live!

I notice the click here to view all search results link is at the top of the code listing now, instead of being with the search bar. That means it'll be invisible most of the time. First, let me say that we're still moving error messages around. We'll probably end up with something like

Re: DXR UI refresh is live!

Fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=969887#c1. It will take effect with the next re-index, in a few hours. Good eye! Somehow, nobody caught this on staging or locally, though it seems obvious in retrospect. While I was at it, I stopped the code from jumping to the side when you

DXR UI refresh is live!

https://blog.mozilla.org/webdev/2014/02/07/dxr-gets-a-huge-ui-refresh/ Happy hacking! ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: DXR UI refresh is live!

that's pretty, but where did the list of classes class members go when viewing files like http://dxr.mozilla.org/mozilla-central/source/modules/libjar/nsZipArchive.cpp Coming back soon: https://bugzilla.mozilla.org/show_bug.cgi?id=965659. We're having some trouble reducing it to a test

Recent and upcoming DXR changes

DXR's been taking patches at a healthy rate, both to the soon-to-land UI branch and directly to production. I wanted to give you an update on what we've grown since November—including some handy but subtle new features you might not have noticed—along with a preview of what's coming next:

Re: Poll: What do you need in MXR/DXR?

What features do you most use in MXR and DXR? One feature I'd like to see in DXR is the ability to click on a header file shown in a #include and have it be opened. For example, if I search for ErrorResult, I see #include mozilla/ErrorResult.h I'd like to be able to click on the

Re: Poll: What do you need in MXR/DXR?

Going back to the idl is probably the best. It isn't just attributes, though, its also structure definitions as well, like: http://dxr.mozilla.org/mozilla-central/source/dom/ipc/PContent.ipdl#l73 So if I'm on this line:

Re: Poll: What do you need in MXR/DXR?

Better python support. For example, the function name parameter doesn't work with ext: .py http://dxr.mozilla.org/mozilla-central/search?q=function%3Astart%20ext%3A.py -- no results http://dxr.mozilla.org/mozilla-central/search?q=%22def%20start%22%20ext%3A.py -- results To clarify,

Re: Poll: What do you need in MXR/DXR?

Thanks, everyone, for your thoughtful and voluminous input! I bequeath you the following behind-the-scenes links so you can see the effect your feedback is having on DXR's future. We've collected, de-duped, and categorized your feedback at https://wiki.mozilla.org/DXR_UI_Refresh#Feedback. If

Re: Poll: What do you need in MXR/DXR?

- Clicking on macros seem to lead to some results, but definitely not the one I'd expect - the definition of the macro. For example, if you click ROLE at http://dxr.mozilla.org/mozilla-central/source/accessible/src/base/RoleMap.h#l34, does the Jump to definition item from the context menu

Re: Poll: What do you need in MXR/DXR?

What a lot of great input! Thank you! I'll reply individually to those I've missed in the days after the Summit. In case you happen to be at the Mozilla Summit in Santa Clara, we're holding a DXR design session to mash all that juicy input together and make sure we have a UI/UX sketch that

Re: Poll: What do you need in MXR/DXR?

Added with gusto. This actually drives me crazy, too. :-) On Oct 2, 2013, at 14:47 , Dave Townsend dtowns...@mozilla.com wrote: Things that drive me nuts about mxr when I've tried to use it: * When navigating down the directory/file tree, it keeps autofocusing the search field, which is

Re: Poll: What do you need in MXR/DXR?

That should be easy enough; I expect it doesn't have any dependencies the mainline moz-central has. I'll add it to the list to try for in Q4! On Oct 2, 2013, at 13:33 , Mike Conley mcon...@mozilla.com wrote: I love DXR for mozilla-central, and would love it if the UX branch

Poll: What do you need in MXR/DXR?

What features do you most use in MXR and DXR? Over in the recently renamed Web Engineering group, we're working hard to retire MXR. It hasn't been maintained for a long time, and there's a lot of duplication between it and DXR, which rests upon a more modern foundation and has been developing

Re: Poll: What do you need in MXR/DXR?

- Easy access to hg annotate, as in mxr (could be better than mxr even, by integrating into the existing view instead of being a separate view). Assuming I understand you right, we've just added this last week. :-) See the Blame link at