Re: Github

Bhavya shah

Hi Brian,
I'll probably be happy to consider putting up the conceptualized blog
post not on the NV Access website, but on the NVDA Community Wiki,
which is a place for these odd titbits of guides and tutorials
contributed by the community rather than being affiliated to the NV
Access organisation itself.

On 9/6/17, Brian's Mail list account via Groups.Io
<> wrote:
I think if you feel it good enough putting it up on the NV access site would

also be a good move, as these questions about what to include and what not
to include seem to occur here quite a lot from time to time. I find the new

headings OK on the issues system but i tend to write my submissions offline

in notepad so most of the info is in the first field. I don't think this
should really matter as long as all the info is there.

At the moment I've not had time to report that loss of first letter issue in

Firefox on some web site links and text as it takes a significant amount of

time to test all the various situations that might cause such a thing. I'm

not convinced its not a bit of short cutting on web site design that has the

undesired effect. Brain
Sent via blueyonder.
Please address personal email to:-, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Bhavya shah" <>
To: <>
Sent: Wednesday, September 06, 2017 11:47 AM
Subject: Re: [nvda] Github

Hi all,
I see that a lot of NVDA users seem interested in helping out with
testing NVDA, sharing feedback, reporting bugs, etc. As an active
triager on the NVDA Github issue tracker (along with some other NVDA
community members), we try to make sure that all tickets are
systematic and well-defined, so that developers have sufficient
diagnostic information or compelling use cases ensuring that the
accepted suggestions are easy better understood and consequently
simpler to implement. Therefore, I fortunately have notable experience
in the past month or so with the issue filing side of Github,
knowledge that I would definitely be interested in passing on. I am
considering writing a comprehensive multi-part guide about filing
issues about NVDA on the Github tracker and other less emphasized and
unmentioned essentials you may want to keep in mind while doing the
same in the form of a blog post on my personal blog (Hiking Across
Horizons - Unfortunately, I will not be
able to get to this blog post idea till the 27th September at least
due to upcoming academic commitments, so please expect to hear from me
in this regard post that date, hopefully. Just thought I'd give a

On 9/6/17, Brian's Mail list account via Groups.Io
<> wrote:
It did not work in firefox either, I think short fragments of the log in

body are OK its other files that you really need to attach in case they

It seems to me that the browse, um does not browse ..!
Sent via blueyonder.
Please address personal email to:-, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Sarah k Alawami" <>
To: <>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github

How odd. What shoudl happen si syou hit brows and the file dialogue
appear, it does under safari. Try chrome maybe and see if that works and

firefox or edge?

Good luck.
On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra
<> wrote:


Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather

simply pasting in the contents of the log file, for instance . The

is that I cannot get any option to attach a file when I clicked on the
“browse” button. It would be a great help if you could explain how to
attach a file using NVDA.

All the best,


m +353 (0)833323487 Ph: _353 (0)1-2864623 e:

From: <>
[ <>] On Behalf Of
Quentin Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: <>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or

report something that isn't working / could work better / should be
implemented etc, what you want to do is create a new issue. The link to
the issues section is

Unless you are writing code yourself, you can mostly ignore the other
sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to

for the issue you want to report. (the first one searches code and

things, you want to search issues). So, if someone reported a problem
with footnotes in Word 2016 for instance, I'd search for "word 2016
footnotes" or similar in that second edit box. There are two types of
issues, open and closed. Open issues are either new issues that haven't
been triaged yet (that is, no one has looked at them to see how serious
they are, whether the issue has already been reported etc), or issues
which are being worked on, or waiting to be worked on. Closed issues

issues which have either been fixed, or which are duplicates of other
issues, or sometimes things which can't or won't be fixed. If the

with footnotes is that you want them to appear at the top of the page

instance, then that isn't something related to NVDA. That's a feature
request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump
straight there with

When you create a new issue, there is a block of text in the "comment"
prompting you for the kinds of information that are useful in diagnosing
the issue. Please try and include: steps to reproduce the issue, attach
any files which might help (eg if Word crashes every time you try and
check formatting in this particular file, if you can share it, that

help), what should happen and what actually happens, and your system
configuration (Windows version, application version, NVDA version and
whether installed or portable), and anything you've done to try and
resolve or get more information (eg tried different version of NVDA or
other program). Don't stress if you don't have every piece of that
information or if you aren't sure if the issue has been filed before.
When someone goes to triage the issue, they will ask for more

if needed. If the issue has been filed previously, they will link to it
(and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards


On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <
<>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site. I haven't signed up
yet but it looks easy to do so and to create a pull request, which I
assume is what is generally referred to on this list as a ticket. But
many people may find the page confusing. Is there a way that some sort

short help information can be inserted after the navigation links on the
page, instructing people what to do to create what are called tickets,
perhaps also how to search for tickets and how to create an account? If
tickets are desired from the widest variety of users, this process

be somehow explained and done so in a place that those wishing to create
tickets will be likely to see the explanation.


Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: <> <>
Twitter: @NVAccess

Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons:

Contacting Me
E-mail Address:
Follow me on Twitter @BhavyaShah125 or
Mobile Number: +91 7506221750

Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons:

Contacting Me
E-mail Address:
Follow me on Twitter @BhavyaShah125 or
Mobile Number: +91 7506221750

Join to automatically receive all group messages.