Can someone point out what's syntactically wrong with this source filter (as documented here - https://nim-lang.org/docs/filters.html) as it refuses to compile with an "invalid indentation" error message
#? stdtmpl | standard
#proc greet(name = "world"): string =
# result = ""
<h1>Hello $name</h1>
#end proc
echo greet()
Since echo greet() is Nim code, you need to prefix it with #. Also, be aware that you may not have empty lines outside the proc, because Nim would then try to append them to a result variable, which does not exist outside the proc.
#? stdtmpl | standard
#proc greet(name = "world"): string =
# result = ""
<h1>Hello $name</h1>
#end proc
#echo greet()
Is there a way to require admin in Autoit only if statement is true?
I tried
Global $a = 0
If $a == 1 Then
#RequireAdmin
EndIf
But that doesn't seem to work, it still asks for Admin rights.
If it's no problem if there are more files:
$a = 1
If($a = 1) Then
Run(Run Script with #RequireAdmin)
Else
Run(Run Script without #RequireAdmin)
EndIf
you could use this:
#include <MsgBoxConstants.au3>
If IsAdmin() Then
MsgBox($MB_SYSTEMMODAL, "", "IsAdmin" & #CRLF & "Admin rights are detected.")
EndIf
If not isAdmin and your var = true then ...
In a rather large code base with a few layers is there a way in vim or from the command line to find all classes that are derived from a base class? grep is an option but can be slow since grep does not index.
Neither cscope nor ctags allow us to deal with inheritance directly but it's relatively easy to work around that limitation because derived classes are also indexed.
cscope
In cscope, looking for "C symbol" Foobar usually lists the original class and classes inheriting from it. Since the search is done against a database, it is lightning fast.
Alternatively, you could use cscope's egrep searching capabilities with a pattern like :.*Foobar to list only classes inheriting from Foobar.
So, even if we don't have a dedicated "Find classes inheriting from this class" command, we can get the work done without much effort.
ctags
While ctags allows you to include inheritance information with --fields=+i, that information can't be used directly in Vim. The inherits field is parsed by Vim, though, so it might be possible to build a quick and dirty solution using taglist().
ack, ag
Those two programs work more or less like grep but they are targeted toward searching in source code so they are really faster than grep.
In my Vim config, :grep is set to run the ag program instead of the default grep so, searching for classes derived from the class under the cursor would look like:
:grep :.*<C-r><C-w><CR>
Here are the relevant lines from my ~/.vimrc:
if executable("ag")
set grepprg=ag\ --nogroup\ --nocolor\ --ignore-case\ --column
set grepformat=%f:%l:%c:%m,%f:%l:%m
endif
If you build your tags files with Exuberant CTags using inheritance information (see the --fields option), then the following script will work. It adds an :Inherits command which takes either the name of a class (e.g. :Inherits Foo) or a regular expression.
Like the :tag command, you indicate that you want the search with a regex by preceding it with a '\' character, e.g. :Inherits \Foo.*.
The results are put into the window's location list, which you browse with :ll, :lne, :lp, etc. VIM doesn't seem to allow scripts to modify the tag list which is what I'd prefer.
If you're wondering why I don't use taglist() for this, it's because taglist() is incredibly slow on large tag files. The original post had a version using taglist(), if you're curious you can browse the edit history.
" Parse an Exuberant Ctags record using the same format as taglist()
"
" Throws CtagsParseErr if there is a general problem parsing the record
function! ParseCtagsRec(record, tag_dir)
let tag = {}
" Parse the standard fields
let sep_pos = stridx(a:record, "\t")
if sep_pos < 1
throw 'CtagsParseErr'
endif
let tag['name'] = a:record[:sep_pos - 1]
let tail = a:record[sep_pos + 1:]
let sep_pos = stridx(tail, "\t")
if sep_pos < 1
throw 'CtagsParseErr'
endif
" '/' will work as a path separator on most OS's, but there
" should really be an OS independent way to build paths.
let tag['filename'] = a:tag_dir.'/'.tail[:sep_pos - 1]
let tail = tail[sep_pos + 1:]
let sep_pos = stridx(tail, ";\"\t")
if sep_pos < 1
throw 'CtagsParseErr'
endif
let tag['cmd'] = tail[:sep_pos - 1]
" Parse the Exuberant Ctags extension fields
let extensions = tail[sep_pos + 3:]
for extension in split(extensions, '\t')
let sep_pos = stridx(extension, ':')
if sep_pos < 1
if has_key(tag, 'kind')
throw 'CtagsParseErr'
endif
let tag['kind'] = extension
else
let tag[extension[:sep_pos - 1]] = extension[sep_pos + 1:]
endif
endfor
return tag
endfunction
" Find all classes derived from a given class, or a regex (preceded by a '/')
" The results are placed in the current windows location list.
function! Inherits(cls_or_regex)
if a:cls_or_regex[0] == '/'
let regex = a:cls_or_regex[1:]
else
let regex = '\<'.a:cls_or_regex.'\>$'
endif
let loc_list = []
let tfiles = tagfiles()
let tag_count = 0
let found_count = 0
for file in tfiles
let tag_dir = fnamemodify(file, ':p:h')
try
for line in readfile(file)
let tag_count += 1
if tag_count % 10000 == 0
echo tag_count 'tags scanned,' found_count 'matching classes found. Still searching...'
redraw
endif
if line[0] == '!'
continue
endif
let tag = ParseCtagsRec(line, tag_dir)
if has_key(tag, 'inherits')
let baselist = split(tag['inherits'], ',\s*')
for base in baselist
if match(base, regex) != -1
let location = {}
let location['filename'] = tag['filename']
let cmd = tag['cmd']
if cmd[0] == '/' || cmd[0] == '?'
let location['pattern'] = cmd[1:-2]
else
let location['lnum'] = str2nr(cmd)
endif
call add(loc_list, location)
let found_count += 1
endif
endfor
endif
endfor
catch /^OptionErr$/
echo 'Parsing error: Failed to parse an option.'
return
catch /^CtagsParseErr$/
echo 'Parsing error: Tags files does not appear to be an Exuberant Ctags file.'
return
catch
echo 'Could not read tag file:' file
return
endtry
endfor
call setloclist(0, loc_list)
echo tag_count 'tags scanned,' found_count 'matching classes found.'
endfunction
command! -nargs=1 -complete=tag Inherits call Inherits('<args>')
In lh-cpp, I define the command :Children. It relies on a ctags database, and as a consequence, it is quite limited.
It takes two optional parameters: the namespace where to look for (I haven't found a way to avoid that), and the name of the parent class -> :Children [!] {namespace} {parent-class}.
The command tries to cache as much information as possible. Hence, when pertinent information changes in the ctags database, the cache must be updated. It is done by banging the command -> :Children!
I don't think vim is the correct tool to list all child classes. Instead, we'd better use the doxygen to generate documentation for the source code. Although the doxygen needs some time, we can use the document/diagrams for all classes, which is clear and fast.
I created a function with an inputdialog to move lines conditionally (tnx to Romainl).
First thing to do is a search, then to invoke the code below.
My Code:
if !exists("char")
let char = "Move Lines with search match after/before?
\ \n
\ \nMove Line Backwards: Start input with: '?'
\ \nMove Line Forwards: Start input with: '/'
\ \n
\ \np.e.
\ \n?=\\s*$
\"
endif
let a = inputdialog(char)
if a == ""
return
endif
if matchstr(a, '^?') != ''
let minplus = '-'
elseif matchstr(a, '^/') != ''
let minplus = '+'
else
echo "wrong input: input does not start with '?' or '/'"
return
endif
I would like to change the "return" command in a "return back to inputdialog" command:
I would like to check the input entered in the inputbox immediately without leaving the inputbox, is that possible?
The call to inputdialog() is a single, blocking call in Vimscript. None of your code can run while it's open. No events (that can be hooked into with :autocmd are fired. In general, there's no parallelism in Vim.
The best you can do is re-launch the inputdialog() (possibly initialized with the previously entered text) when the validation fails.
Alternatively, you'd have to implement your own input control (e.g. using getchar()). There, you can run validation while waiting for the next pressed character.
I'm setting up unit testing for the first time on my Zend Framework app (and it's actually the first time I'm doing unit testing at all).
A problem I'm getting at the moment is that I use a view helper to include my headscripts and links:
class Zend_View_Helper_HeadIncludes extends Zend_View_Helper_Abstract {
public function headIncludes($type, $folder) {
if($folder == "full" && APPLICATION_ENV == "production") {
$folder = "min";
}
$handler = opendir(getenv("DOCUMENT_ROOT") . "/". $type ."/" . $folder);
while ($file = readdir($handler)) {
if ($file != "." && $file != "..") {
if($type == "js") {
$this->view->headScript()->appendFile('/js/' . $folder . '/' . $file);
} else if ($type == "css" ) {
$this->view->headLink()->appendStylesheet('/css/' . $folder . '/' . $file);
}
}
}
closedir($handler);
}
}
This is included in each view script. When I try and run a test it fails because opendir() tries to find eg "/css/full" relative to the document root, which seems to not be the same value for tests and the application. What's the best way to resolve this? I could add in a conditional to do something different when APPLICATION_ENV = "testing", but am not sure if this would run contrary to what setting up testing is supposed to achieve.
The environment variable 'DOCUMENT_ROOT' is only going to be set by your web server. You may want to be using 'APPLICATION_PATH' as a reference instead as it's more reliable across virtual hosts as well as command line usage.