Author Topic: next_error not working after concur_command  (Read 879 times)

rowbearto

  • Senior Community Member
  • Posts: 1769
  • Hero Points: 119
next_error not working after concur_command
« on: October 05, 2018, 06:58:32 pm »
Before beta5, when I did a concur_command that ran a command that outputted some formatted build errors, when I did a subsequent "next_error", I would be taken to the next error. This seems to have broken in beta5.

The actual SlickC code looks something like this:

Code: [Select]
    activate_build();
    reset_next_error();
    _str cmdToSend = ...
    concur_command(cmdToSend);

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5435
  • Hero Points: 444
Re: next_error not working after concur_command
« Reply #1 on: October 05, 2018, 08:36:41 pm »
I just tried a sample running a program called "whatever" (actually sgrep). Worked for me. Does it work for you in a default config (just load a small macro or run a batch macro like I did)? Not sure what could affect this though.

rowbearto

  • Senior Community Member
  • Posts: 1769
  • Hero Points: 119
Re: next_error not working after concur_command
« Reply #2 on: October 05, 2018, 08:52:34 pm »
Look for rowbearto.user.cfg.xml on support.

It does work with a clean config, but I do have the problem with my specific config - so try my user.cfg.xml.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5435
  • Hero Points: 444
Re: next_error not working after concur_command
« Reply #3 on: October 05, 2018, 10:16:38 pm »
Still works for me with your config.

Here's what I'm doing.

* Start SlickEdit with a clean config
* Exit editor
* Replace user.cfg.xml with yours
* Start SlickEdit
* Run my batch macro
Code: [Select]
...
defmain()
{
    activate_build();
    reset_next_error();
    // Whatever runs sgrep.
    // Didn't want to use any typically named executable which
    // might have special case code for it.
    command:='whatever main "/home/cmaurer/*.cpp"';
    concur_command(command);
}
* Do next error with Ctrl+Shift+Down

rowbearto

  • Senior Community Member
  • Posts: 1769
  • Hero Points: 119
Re: next_error not working after concur_command
« Reply #4 on: October 06, 2018, 02:48:07 pm »
Exited and restarted SlickEdit, it is not occurring now.

I'll try to retrace my steps from yesterday see if I can get it back into this strange state.