In your FindInFiles command it is not specified where to search. You have not posted which version of UltraEdit you use and therefore can't tell you if this is a known bug of the macro recorder or not.

Correct would be something like:

InsertMode
ColumnModeOff
HexOff
IfSel
FindInFiles OutputWin OpenFiles "" "" "^s:"
Else
SelectWord
IfSel
FindInFiles OutputWin OpenFiles "" "" "^s:"
EndIf
EndIf

or

InsertMode
ColumnModeOff
HexOff
IfSel
FindInFiles OutputWin "C:\Temp\" "*.asm" "^s:"
Else
SelectWord
IfSel
FindInFiles OutputWin "C:\Temp\" "*.asm" "^s:"
EndIf
EndIf

In the macro environment it is not possbile to access the content in the output window. So your second wish to open the first file and position the cursor to the found line is not possible with a macro. It would be possible with a script depending on the version of UltraEdit you use. So you have to double click on the line itself in the output window or use Ctrl+Shift+Down Arrow if you use UE v15.00+.

Cyrex wrote:If I output to editor, then the macro environment can access it, can it then open the wanted file location?

You could open the file, but positioning the cursor at correct line is not possible with a macro because you can't convert the line number as string into an integer number for being used in a GotoLine command. Also the macro environment does not support variables. The only possibility would be to run from within the macro a user tool which calls UltraEdit with the "file name/line number" as parameter and when allow multiple instances is not enabled the file should be opened in the current instance of UltraEdit with cursor positioned on the correct line. So a script would be definitely better.

Even better than a script is using Ctags and the command Search - Find Symbol (with a hotkey). Because you are working already with a project using Ctags here should be your first choice as I would use too. To be more precise I have a C167 project with source files mainly written in C but contains also 3 assembler files and I use Ctags for that project. Search - Find Symbol to jump to a label in the assembler file based on the word at current cursor position (selecting the word is not necessary) works fine and with Search - Back (last position) I can jump back. Both commands are assigned to hotkeys. That should work also in your project. I think, you don't really need special Ctags parameters because assembler languages are supported natively by Ctags. So the standard Ctags parameters -L %fi -f %fo should be enough. So all you need to do is to specify in the project settings dialog the name and location for the ctags database file and create the database by executing Project - Create CTAG file.

Also possible would be to add to your wordfile a regular expression function string which finds labels in your assembler files and list them in the function list. I have not done this because an assembler file contains so many labels that this does not make really sense. So the function list for my C167 assembler files shows only the names of the procedures.

Looks like Ctags does not recognize your assembler files correct. Maybe you are not using a common file extension for your assembler files. I use following Ctags Options for my project:

-I _atbit+ --langmap=c:.c.h.inc,asm:.asm.def -L %fi -f %fo

-I _atbit+
is just for telling Ctags that _atbit is a special token. It is a special type to define a bit variable at a fixed location in the bitaddressable RAM of the C167 controller. You can forget that for your project.

--langmap=c:.c.h.inc,asm:.asm.def
is more interesting for you because it maps the files *.c, *.h and *.inc to the 'C' symbol parser, and *.asm and *.def to the ASM symbol parser. Maybe you need to do something similar for your project.

-L %fi -f %fo
is the standard and just tells Ctags to parse the lines from the file UltraEdit creates dynamically (%fi is the placeholder for the name of this list file) and should write data to the file you have specified in the project settings dialog (%fo is the placeholder for that file name).

I can see in the tag file created by Ctags that it contains all labels, procedure names, section names and register bank names. It contains also some assembler directives which are not really symbols, but that doesn't matter.

If you get a different result, you need to invest some time to read the documentation of Ctags and fine tune it for your requirements. You probably need to specify your own Perl regular expressions to find the symbols in your assembler files you want in the database. I can't really help you here because I never needed to read-in so deeply into the Ctags manual.

I don't know what cscope is nor do I have Python installed. Ctags works fine for me (older projects) as well as the integrated parser for UEStudio (new projects). So thanks for your offer, but I don't need anything additional.