[Github-comments] [geany/geany-plugins] [geanylua] geany.scintilla() does not work with SCI_SETLEXER (#646)

[Skif-off]

@elextr 
>>> Its any name known to your system iconv, so its system specific, Geany has some common names in its menus, but in fact even those are not guaranteed to be available.

>> Thanks, here it is necessary to think.

> As far as we know there is no programmatic way of getting a list of the available encodings at runtime, (the equivalent of the iconv --list command). If you find one let us know.

Well, now I understand why I did not find examples of using this feature :))

> and probably the build scripts are very specific to the particular setup and would not be useful even if they were published.

I don't think so and they are not much different from Debian repositories ([geany](https://anonscm.debian.org/git/pkg-geany/packages/geany.git), [geany-plugins](https://anonscm.debian.org/git/pkg-geany/packages/geany-plugins.git)) :) I use Debian-based OS and I wanted to see ```geany-plugins-common.install``` (```libgeanypluginutils.so*```) only (I think that ```geany-plugin-workbench.install``` & ```geany-plugin-keyrecord.install``` like all the others).
But now I think I understood how to do it, I will check it.
(I'm make deb files for myself because I'm using PR [#1017](https://github.com/geany/geany/pull/1017) for Geany.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/646#issuecomment-348099123
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20171130/d845f86b/attachment-0001.html>