-
![ads](https://cloud.githubusercontent.com/assets/14153331/11699862/32d5271c-9ecf-11e5-97d2-55ec9a8036b3.png)
QRL-394-19463
-
Hi Kim,
Today I did the upgrade repository, and test the dashboard observed:
That being connected to a reflector D-Star, not shown in linkto
![captura de pantalla 2016-05-24 a las 1 08 57 p m](http…
YV5OF updated
8 years ago
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
It would be nice if you can support **GNU Global** or **Cscope** as I find ctags inadequate for large code bases.
Good work.
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…
-
```
The previous 2.0 can provide chunk name and line number in error string
when a lua parsing error occurs, but not when an exception is thrown from
.NET code.
I looked through the code and found th…