• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Does Gedit have user definable languages? If not, then no.
 
Does Gedit have user definable languages? If not, then no.

It does, but I think it's set up different from Notepad++.
 
It does, but I think it's set up different from Notepad++.
Notepad++ can be installed on Linux through Wine or atleast it could in the previous version I did it on).
 
I find it helpful to have a 6th Keywords List for the default traits (for spelling, etc.). Here's the complete list (extracted from 00_traits.txt, 01_traits.txt, and 02_traits.txt):

Code:
amateurish_plotter
flamboyant_schemer
intricate_webweaver
elusive_shadow
naive_appeaser
underhanded_rogue
charismatic_negotiator
grey_eminence
indulgent_wastrel
thrifty_clerk
midas_touched
misguided_warrior
tough_soldier
skilled_tactician
brilliant_strategist
detached_priest
martial_cleric
scholarly_theologian
mastermind_theologian
stressed
depressed
ill
pneumonic
syphilitic
leper
wounded
maimed
infirm
incapable
drunkard
has_tuberculosis
has_typhoid_fever
has_typhus
has_bubonic_plague
has_measles
has_small_pox
crusader
bastard
twin
legit_bastard
pregnant
excommunicated
kinslayer
homosexual
clubfooted
harelip
hunchback
lisp
stutter
fair
ugly
dwarf
genius
quick
slow
imbecile
inbred
strong
weak
celibate
hedonist
scholar
gardener
mystic
impaler
duelist
hunter
poet
falconer
lustful
chaste
gluttonous
temperate
greedy
charitable
slothful
diligent
envious
kind
wroth
patient
proud
humble
deceitful
honest
craven
brave
shy
gregarious
ambitious
content
arbitrary
just
cynical
zealous
paranoid
trusting
cruel
light_foot_leader
heavy_infantry_leader
cavalry_leader
inspiring_leader
trickster
organizer
defensive_leader
experimenter
flanker
aggressive_leader
siege_leader
mujahid
hajjaj
on_hajj
faqih
hafiz
sayyid
pilgrim
mirza
scarred
eunuch
blinded
born_in_the_purple
augustus
flat_terrain_leader
rough_terrain_leader
mountain_terrain_leader
desert_terrain_leader
holy_warrior
unyielding_leader
has_aztec_disease
child_of_consort
peasant_leader
heresiarch
berserker
varangian
saoshyant
saoshyant_descendant
viking
monk
nun
on_pilgrimage
sickly
mutazilite
ashari
sympathy_christendom
sympathy_islam
sympathy_pagans
sympathy_zoroastrianism
sympathy_judaism
bad_priest_christian
bad_priest_muslim
bad_priest_norse
bad_priest_tengri
bad_priest_zoroastrian
bad_priest_aztec
narrow_flank_leader
brahmin
kshatriya
vaishya
sympathy_indian
shaivist_hindu
vaishnavist_hindu
shaktist_hindu
smartist_hindu
mahayana_buddhist
vajrayana_buddhist
theravada_buddhist
digambara_jain
svetambara_jain
decadent
reincarnation
war_elephant_leader
jungle_terrain_leader
in_hiding
winter_soldier
seducer
seductress
administrator
architect
strategist
socializer
schemer
theologian
gamer
 
  • 2
Reactions:
Yes, it still works, it just doesn't highlight the newer keywords.
 
I would imagine it could seriously use someone to go through and update it tbh.
 
  • 1
Reactions:
How can you add in an extra beginning scope and end scope , so I would be able to fold all the code between them ?
For example:
############start-abductiontree
character_event = {}
character_event = {}
...
############end-abductiontree
 
I know literally nothing about Notepad++ plugins, but does anyone have an idea of how this could be updated?
 
Language->Choose your language->CK2 in the User Defined Language dropdown->Keyword List->add new keywords to appropriate groups
For updating auto-completion you need to edit the .XML file.

I have no idea if there's a plugin that could accomplish what @burny26 wants.
 
  • 2
Reactions:
I've gone ahead and updated this for 2.5.2. Installation instructions are the same as in the OP, as are colors:
Instructions:
If you have previous version you must first remove old language file, to do so in Notepad++ open "Language/Define your language...", in "User language" box at the top select CK2, select "Remove".

The zip file contains two files - CK2.xml and CK2lang.xml. Place CK2.xml in directory where you installed "Notepad++/Notepad++/plugins/API" (default path would be "C:/Program Files/Notepad++/plugins/API"). Run Notepad++ open "Language/Define your language...", click Import and chose CK2lang.xml. Open "Settings/Preferences/Auto-Completion" and check "Enable auto-completion on each input" and "Function completion".

After installing, you may need to close and reopen Notepad++ before it shows up in the language selection dropdown.

I used the wiki pages for reference, and I probably missed some stuff, so I'm not sure how complete it is or how much stuff is out of date and should be removed. If you find something missing, in the wrong category, or that should be removed, feel free to post here and I can update.

@talias, if you'd rather I remove this I'll do so.
 

Attachments

  • ck2_n++_252_3.zip
    19,9 KB · Views: 21
  • 1
  • 1
Reactions:
Thank you!
 
I didn't add in Wyhorn's list of traits or try to figure out burny26's suggestion, but I might go back later and work on those.

Edit: Oh, and it should be fully compatible with zimxavier's localization highlighting, though I haven't tested it.
 
Last edited:
OK, I'm kind of spamming this thread, but I was bored so I implemented @burny26's suggestion. You can now use comments to collapse larger blocks than just one pair of brackets (for example, you could use this to make an entire event change one collapsible element, if all the events were together). To avoid making every single comment collapsible, I had to add a unique syntax for collapsible comments.

So:
To begin a collapsible section, follow the comment sign "#" with an exclamation point. If you add a space after the exclamation point, you can then write whatever comment you want.
To end a collapsible section, follow the comment sign "#" with two exclamation points. If you add a space after the exclamation points, you can then write whatever comment you want.

For example:
Code:
event_0 = {}
#! start of my event chain
event_1 = {}
event_2 = {}
event_3 = {}
#!! end of my event chain
event_4 = {}
Everything between the line starting with #! and the line starting with #!! (events 1-3) will be collapsible just like everything within a set of brackets is collapsible.

I updated the post where I posted the first update with this new version.
 
Last edited:
  • 1
Reactions:
OK, I'm kind of spamming this thread, but I was bored so I implemented @burny26's suggestion. You can now use comments to collapse larger blocks than just one pair of brackets (for example, you could use this to make an entire event change one collapsible element, if all the events were together). To avoid making every single comment collapsible, I had to add a unique syntax for collapsible comments.

So:
To begin a collapsible section, follow the comment sign "#" with an exclamation point. If you add a space after the exclamation point, you can then write whatever comment you want.
To end a collapsible section, follow the comment sign "#" with two exclamation points. If you add a space after the exclamation points, you can then write whatever comment you want.

For example:
Code:
event_0 = {}
#! start of my event chain
event_1 = {}
event_2 = {}
event_3 = {}
#!! end of my event chain
event_4 = {}
Everything between the line starting with #! and the line starting with #!! (events 1-3) will be collapsible just like everything within a set of brackets is collapsible.

I updated the post where I posted the first update with this new version.
@Ekyman , very nice work! Works like a charm! :)
 
OK, I'm kind of spamming this thread, but I was bored so I implemented @burny26's suggestion. You can now use comments to collapse larger blocks than just one pair of brackets (for example, you could use this to make an entire event change one collapsible element, if all the events were together). To avoid making every single comment collapsible, I had to add a unique syntax for collapsible comments.

So:
To begin a collapsible section, follow the comment sign "#" with an exclamation point. If you add a space after the exclamation point, you can then write whatever comment you want.
To end a collapsible section, follow the comment sign "#" with two exclamation points. If you add a space after the exclamation points, you can then write whatever comment you want.

For example:
Code:
event_0 = {}
#! start of my event chain
event_1 = {}
event_2 = {}
event_3 = {}
#!! end of my event chain
event_4 = {}
Everything between the line starting with #! and the line starting with #!! (events 1-3) will be collapsible just like everything within a set of brackets is collapsible.

I updated the post where I posted the first update with this new version.

Nice. I imagine we can also nest comments like we can nest brackets, right?
 
did you include the new scopes like any_character ?