Recent Posts

Pages: [1] 2 3 ... 10
1
SlickEdit® / How to tag assembler files together with C in a Project
« Last post by hebsahid on Today at 04:48:11 pm »
I have the following problem with SlickEdit 2013 (v18.0.1.2)

My project includes files from C, C++, Java, Python and Intel assembler.

When creating my project I choose the directory where all my source tree is located and all files are included in the project. ( I have tried with  C/C++ and Other language when creating the project)

I can start searching by Variables in C, C++, Java and Python projects and it finds and list all definitions of variables except the ones in assembler files.

Once I open the assembler file and do the search again, now it lists the variable, and that variable will be saved for next times I search for this with the file closed.

But I do not want to open all assembler files (900+) and search first for all the variables to allow SlickEdit to "remember" what is supposed to be done with the tagging of the project.

I have created an assembler tag file, but it is not linked to projects, in this case it works fine, but I lose the tagging of all other source and when changing project I need to also manually change the tag file.

Any idea how to make it work automatically?

Regards.
2
SlickEdit® / Re: The difference between vi and emacs editor window mode?
« Last post by Clark on Today at 03:50:35 pm »
Often it looks like changing the "Files per window" isn't working due to auto-restore. Auto-restore doesn't care what the "Files per window" setting is and will restore a workspace or invocation exactly the way things were before. By deleting your config, you cleared the auto-restore information used by an invocation (you could just delete vrestore.slk). This doesn't clear auto-restore information in your workspaces though.

Also keep in mind that changing the "Files per window" setting doesn't change the windows/tabs/buffer layout you currently have.

Hope this helps.
3
SlickEdit® / Re: How to add thread number to vsmktags?
« Last post by Dennis on Today at 02:06:14 pm »
In terms of I/O, the largest bottleneck is generally where the tag file is written.  As Graeme suggests, adjust Workspace Properties to put the workspace tag file on a fast SSD or if you have enough memory, a RAM disk, and you'll see a big improvement.

Also, if you have enough memory, try adjusting Tools > Options > Background Tagging > Background Tagging Threads > Maximum number of active tagging jobs and Maximum amount of background tagging memory usage (MB).  Give both of them an order of magnitude increase (10,000 and 256 MB), and you'll also see some gains.

The other thing I'd like to point out, and I see this a lot, is that if those 100,000 files are 10 copies of different versions of a set of 10,000 files, then, well, don't do that, it's just not good practice to toss everything into the blender.  It just makes things harder for the tagging engine without providing you with any real benefit.  Create a separate workspace for each version of the files.
4
I delete all configuration files and reset again, now this setting works.

Thanks!
5
SlickEdit® / The difference between vi and emacs editor window mode?
« Last post by onlyflyer on May 21, 2017, 11:46:01 pm »
Hi,
I used emacs emulation before and recently I changed it to vi.

One thing I noticed is the if I open a new file in a window, emacs mode will use this file to occupy the editor window, but vi mode it will open a new tab and this file will share the window with the previous files.

I don't like the vi mode and I found a option to disable it by:

editting->editor window->one file per window.

It works will before, but today it doesn't work. In vi mode, different files tab share the same window again. I loaded the 21.0.2 hot fix yesterday and I am not sure if it is the hot fix break this setting.

Anyone has any idea to help on this issue?

Thanks!
6
SlickEdit® / Re: How to add thread number to vsmktags?
« Last post by mjdl on May 21, 2017, 04:56:02 pm »
I think it shouldn't take an hour.  Maybe it's disk bound.  Are the source files and tag files both on the server?
Am I wrong in speculating (technically naive, of course!) that whether or not the tagging process is started by the editor or from the command line, it will still execute on the client workstation and thus be limited by the I/O of the client/server link? In other words, the server CPU is only doing network/disk I/O in this scenario, and there would have to be a really high-bandwidth I/O to saturate the CPU, and in fact the server OS may scale down the CPU demands of the I/O process for other reasons.

Wouldn't somehow making the tagging process execute on the server be a better approach, since then the only limiting factor is the number of cores and local disk I/O? Perhaps via a daily scheduled command-line job on the server, so that the client workstation Slickedit tagging process would effectively only need to keep track of which files needed retagging in the course of work. Of course, adjusting the Slickedit client to cache in memory all the tag files on the server would be necessary.

As I say, I'm not exactly very well informed about all the pieces of the puzzle...
7
SlickEdit® / Re: How to add thread number to vsmktags?
« Last post by Graeme on May 20, 2017, 09:53:55 pm »
I think it shouldn't take an hour.  Maybe it's disk bound.  Are the source files and tag files both on the server?  You can change the location of the tag file via "workspace properties" on the project menu.  In tools -> options -> application options -> virtual memory, try increasing the tag file cache size.
8
SlickEdit® / Re: How to add thread number to vsmktags?
« Last post by onlyflyer on May 20, 2017, 12:34:40 am »
I did all what you mentioned. Enable all background tagging knob and set the thread number to the max value(8).
But CPU usage is not high, it is 120%~150%.We have many idle cores on server, we hope to make vsmktags much faster.

Thanks!
9
SlickEdit® / Re: How to add thread number to vsmktags?
« Last post by Graeme on May 20, 2017, 12:28:26 am »
Did you run vsmktags.exe from the command line?  It has threaded tagging enabled by default but I don't know how many threads it uses.

In slickedit, go to the help, select the Index tab and type in "threads"  - then look at "use background tagging threads".  In slickedit tools-> options, type "thread" in the search box then go to "background tagging".  You can specify the number of threads to use for tagging and the amount of memory to use.  You have to restart slick to get some of these changes to take effect.

10
SlickEdit® / How to add thread number to vsmktags?
« Last post by onlyflyer on May 20, 2017, 12:06:05 am »
Hi,
I have a big workspace which have more than 100,000 files and our development server has lots of cores.

I find vsmktags only can occupy ~150% CPU. It takes more than one hour to retag the whole workspace.
I am wandering if we can increase the thread number to speed up the retag work.

Thanks,
Hui
Pages: [1] 2 3 ... 10