Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Question: VPP & AUTOs #872

Closed
veripoolbot opened this issue Feb 16, 2015 · 2 comments
Closed

Question: VPP & AUTOs #872

veripoolbot opened this issue Feb 16, 2015 · 2 comments
Labels
question

Comments

@veripoolbot
Copy link
Collaborator

Author Name: Moshe Stolar
Original Redmine Message: 1598 from https://www.veripool.org

Hi,

I'm using the good old VPP.
and I'm tying to use it with the good less old AUTOs.
the problem is that they don't live well together.

the way I'm using now is:
1- parsing the verilog file with the VPP
2- Using the AUTOs compilation on the parsed file.
3- killing the INPUT & OUTPUT (leaving the AUTO instancing only)
this is very annoying!!!

is there a friendlier way to get alone?
moving to generate is not an option ;-)

best solution ;-)
integrate the VPP into XEMACS,
and create AUTO VPP.

BR,
@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2015-02-16T21:47:17Z

It seems you're asking for a VPP feature; while this site does support verilog-mode unfortunately this site has nothing to do with vpp. Or perhaps I'm not understanding your request?

@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Moshe Stolar
Original Date: 2015-02-17T07:01:39Z

Hi,

as you support some basic features of VPP - for indenting & font colors,
I hoped you can also help in supporting that.

it is neither a problem of VPP nor of verilog-mode.
it is a little problem in between VPP & verilog-mode.
since it is not a problem of both, there is a work around (I just need to parse the VPP into verilog, that you support).

still, it might be a nice to have feature.
it is just a wishful feature, rather than a missing feature.

as a fan of xemacs, and it's powerful AUTOs,
I know this will bring more VIM users to work with xemacs ;-)

BR,
Moshe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@veripoolbot