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

Is there a way to support Lazarus trunk installed by fpcupdeluxe? #123

Open
edwinyzh opened this issue Jun 14, 2018 · 1 comment
Open

Is there a way to support Lazarus trunk installed by fpcupdeluxe? #123

edwinyzh opened this issue Jun 14, 2018 · 1 comment

Comments

@edwinyzh
Copy link

As you might know, there is a tool called fpcupdeluxe, which allows you to custom build any versions/compilations of FPC/Lazarus, including the SVN trunk (which I use).

Is there a way (even a manual way) to apply the editor font colors to a Lazarus installation (in any folder, eg. C:\lazarus_trunk) by fpcupdeluxe?

Thanks.

@vhanla
Copy link

vhanla commented Jun 22, 2018

DITE detects installed Lazarus from Windows user's local directory, and if you have installed Lazarus it will have its own directory there, so you can copy XML files from %USERPROFILE%\AppData\Local\lazarus\userschemes into C:\lazarus_trunk\config_lazarus\userschemes then from Lazarus Trunk you will be able to pick them Ctrl+Shift+O (IDE Options —> Editor -> Display -> Colors)

image

[ALTERNATIVE]

However, if you don't have Lazarus installed (normal installation), you can move C:\lazarus_trunk\config_lazarus directory to %USERPROFILE%\AppData\Local\ and rename to lazarus, edit environmentoptions.xml file and modify <LazarusDirectory Value="..\lazarus"> to <LazarusDirectory Value="C:\lazarus_trunk\lazarus"> and also edit C:\lazarus_trunk\lazarus\lazarus.cfg and modify too --primary-config-path=C:\Users\<YOUR_PROFILE_NAME>\AppData\Local\lazarus. Now DITE will detect it.

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

2 participants