Stats

  • Replies 8
  • Subscribers 149
  • Views 274
  • Members are here 0

Accessing SKILL runtime error locations outside the IDE (Vim workflow)

TF202506034656

Good evening,

I primarily develop SKILL in Vim and rarely use the SKILL IDE. The IDE has one feature that I've been looking for ways to emulate. When a runtime error occurs, it focuses the editor on the offending line and highlights it.

Is there any way to access this same functionality through the public API outside of the IDE? I understand highlighting + viewpoint shifting definitely isn't possible, but  I could emulate this myself. 


Anything would help, I could do highlighting if there was some way to at least get the line number.



I'm running version IC23.1-64b and follow the usual load("script.il") in the CIW and execute workflow.

Thanks,

Trevor Farias

Parents
  • RK56

    Hi Trevor,

    May you find the answer you are seeking. I also use Vim more than Skill IDE. I'm curious to know your Vim setup/plugins to write skill scripts. Please share it in a separate post.

    Thanks

    Ram

  • TF202506034656
    in reply to RK56

    Hi Ram,
    I've made a whole host of functions to better facilitate my vim use; most notable is a IDE-linter equivalent that highlights + comments warnings/errors/hints on my vi window, and a lot of mechanisms to avoid repetitive tasks. I'll try and create a forums post tomorrow. As to my answer I seek, I believe Aurel has performed some magic, I'll be testing it tomorrow. 
    Thanks, Trevor

Reply
  • TF202506034656
    in reply to RK56

    Hi Ram,
    I've made a whole host of functions to better facilitate my vim use; most notable is a IDE-linter equivalent that highlights + comments warnings/errors/hints on my vi window, and a lot of mechanisms to avoid repetitive tasks. I'll try and create a forums post tomorrow. As to my answer I seek, I believe Aurel has performed some magic, I'll be testing it tomorrow. 
    Thanks, Trevor

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.