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

I am unable to find Makefile.am #3233

Closed
brewmanz opened this issue Jul 12, 2022 · 6 comments
Closed

I am unable to find Makefile.am #3233

brewmanz opened this issue Jul 12, 2022 · 6 comments

Comments

@brewmanz
Copy link

In https://geany.org/manual/hacking.html (dated 2016-07-26 18:15:59Z) under [filetypes.* configuration file](https://geany.org/manual/hacking.html#id32)
it mentions
Don't forget to add the newly created filetype file to data/Makefile.am
but I cannot find Makefile.am anywhere on my Ubuntu 20.04 computer when filtered by (case ignored) geany.
I am using geany 1.36 (built on 2020-03-22 with GTK 3.24.14, GLib 2.64.1)
I realise that that is 2 years old, but would mention that it's the latest that Ubuntu 20.04 LTS seems to know about.

@elextr
Copy link
Member

elextr commented Jul 12, 2022

Assume your reference is this, it doesn't link.

Hacking (and Makefile.am) is for working on Geany source, so you need to get Geany source. An install from a distro won't have source.

But the section I linked above is for adding a builtin filetype, needing code changes in Geany (which you would not be able to make without source anyway) not a custom filetype as discussed in #3232.

So I suspect this is not what you want to do.

Yes, Ubuntu LTS is well, long term stable, ie it doesn't update to newer versions, those go to the non-LTS first.

@brewmanz
Copy link
Author

Thanks for that. It's just difficult finding which bits are relevant when comments say # For complete documentation of this file, please see Geany's main documentation; technically true but practically not helpful.
I may yet resort to forking the source, but still got a few more rabbit holes to jump down before I exhaust custom filetypes.

@elextr
Copy link
Member

elextr commented Jul 12, 2022

I assume you are still working on Awk. There is no awk specific lexer in lexilla, so (unless you write one) you are stuck using a lexer that is "close enough". So the only reason to add a built-in type for awk would be to get the ctags symbol parser for awk. I'm not sure how up-to-date Hacking is about adding a parser, probably best to examine any recent PRs that do it.

@brewmanz
Copy link
Author

I'm currently working on making an 'awk profile that looks perl with extra/different keywords' approach.

@rdipardo
Copy link
Contributor

There is no awk specific lexer in lexilla

True. But a downstream maintainer has developed one (for GAWK, by the looks of it): https://github.com/zufuliu/notepad2/blob/main/scintilla/lexers/LexAwk.cxx

@kugel-
Copy link
Member

kugel- commented Aug 27, 2022

I think the original issue is resolved.

@kugel- kugel- closed this as completed Aug 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants