Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

[8fe29e]: doc / SciTEDoc.html Maximize Restore History

Download this file

SciTEDoc.html    4133 lines (4114 with data), 186.9 kB

   1
   2
   3
   4
   5
   6
   7
   8
   9
  10
  11
  12
  13
  14
  15
  16
  17
  18
  19
  20
  21
  22
  23
  24
  25
  26
  27
  28
  29
  30
  31
  32
  33
  34
  35
  36
  37
  38
  39
  40
  41
  42
  43
  44
  45
  46
  47
  48
  49
  50
  51
  52
  53
  54
  55
  56
  57
  58
  59
  60
  61
  62
  63
  64
  65
  66
  67
  68
  69
  70
  71
  72
  73
  74
  75
  76
  77
  78
  79
  80
  81
  82
  83
  84
  85
  86
  87
  88
  89
  90
  91
  92
  93
  94
  95
  96
  97
  98
  99
 100
 101
 102
 103
 104
 105
 106
 107
 108
 109
 110
 111
 112
 113
 114
 115
 116
 117
 118
 119
 120
 121
 122
 123
 124
 125
 126
 127
 128
 129
 130
 131
 132
 133
 134
 135
 136
 137
 138
 139
 140
 141
 142
 143
 144
 145
 146
 147
 148
 149
 150
 151
 152
 153
 154
 155
 156
 157
 158
 159
 160
 161
 162
 163
 164
 165
 166
 167
 168
 169
 170
 171
 172
 173
 174
 175
 176
 177
 178
 179
 180
 181
 182
 183
 184
 185
 186
 187
 188
 189
 190
 191
 192
 193
 194
 195
 196
 197
 198
 199
 200
 201
 202
 203
 204
 205
 206
 207
 208
 209
 210
 211
 212
 213
 214
 215
 216
 217
 218
 219
 220
 221
 222
 223
 224
 225
 226
 227
 228
 229
 230
 231
 232
 233
 234
 235
 236
 237
 238
 239
 240
 241
 242
 243
 244
 245
 246
 247
 248
 249
 250
 251
 252
 253
 254
 255
 256
 257
 258
 259
 260
 261
 262
 263
 264
 265
 266
 267
 268
 269
 270
 271
 272
 273
 274
 275
 276
 277
 278
 279
 280
 281
 282
 283
 284
 285
 286
 287
 288
 289
 290
 291
 292
 293
 294
 295
 296
 297
 298
 299
 300
 301
 302
 303
 304
 305
 306
 307
 308
 309
 310
 311
 312
 313
 314
 315
 316
 317
 318
 319
 320
 321
 322
 323
 324
 325
 326
 327
 328
 329
 330
 331
 332
 333
 334
 335
 336
 337
 338
 339
 340
 341
 342
 343
 344
 345
 346
 347
 348
 349
 350
 351
 352
 353
 354
 355
 356
 357
 358
 359
 360
 361
 362
 363
 364
 365
 366
 367
 368
 369
 370
 371
 372
 373
 374
 375
 376
 377
 378
 379
 380
 381
 382
 383
 384
 385
 386
 387
 388
 389
 390
 391
 392
 393
 394
 395
 396
 397
 398
 399
 400
 401
 402
 403
 404
 405
 406
 407
 408
 409
 410
 411
 412
 413
 414
 415
 416
 417
 418
 419
 420
 421
 422
 423
 424
 425
 426
 427
 428
 429
 430
 431
 432
 433
 434
 435
 436
 437
 438
 439
 440
 441
 442
 443
 444
 445
 446
 447
 448
 449
 450
 451
 452
 453
 454
 455
 456
 457
 458
 459
 460
 461
 462
 463
 464
 465
 466
 467
 468
 469
 470
 471
 472
 473
 474
 475
 476
 477
 478
 479
 480
 481
 482
 483
 484
 485
 486
 487
 488
 489
 490
 491
 492
 493
 494
 495
 496
 497
 498
 499
 500
 501
 502
 503
 504
 505
 506
 507
 508
 509
 510
 511
 512
 513
 514
 515
 516
 517
 518
 519
 520
 521
 522
 523
 524
 525
 526
 527
 528
 529
 530
 531
 532
 533
 534
 535
 536
 537
 538
 539
 540
 541
 542
 543
 544
 545
 546
 547
 548
 549
 550
 551
 552
 553
 554
 555
 556
 557
 558
 559
 560
 561
 562
 563
 564
 565
 566
 567
 568
 569
 570
 571
 572
 573
 574
 575
 576
 577
 578
 579
 580
 581
 582
 583
 584
 585
 586
 587
 588
 589
 590
 591
 592
 593
 594
 595
 596
 597
 598
 599
 600
 601
 602
 603
 604
 605
 606
 607
 608
 609
 610
 611
 612
 613
 614
 615
 616
 617
 618
 619
 620
 621
 622
 623
 624
 625
 626
 627
 628
 629
 630
 631
 632
 633
 634
 635
 636
 637
 638
 639
 640
 641
 642
 643
 644
 645
 646
 647
 648
 649
 650
 651
 652
 653
 654
 655
 656
 657
 658
 659
 660
 661
 662
 663
 664
 665
 666
 667
 668
 669
 670
 671
 672
 673
 674
 675
 676
 677
 678
 679
 680
 681
 682
 683
 684
 685
 686
 687
 688
 689
 690
 691
 692
 693
 694
 695
 696
 697
 698
 699
 700
 701
 702
 703
 704
 705
 706
 707
 708
 709
 710
 711
 712
 713
 714
 715
 716
 717
 718
 719
 720
 721
 722
 723
 724
 725
 726
 727
 728
 729
 730
 731
 732
 733
 734
 735
 736
 737
 738
 739
 740
 741
 742
 743
 744
 745
 746
 747
 748
 749
 750
 751
 752
 753
 754
 755
 756
 757
 758
 759
 760
 761
 762
 763
 764
 765
 766
 767
 768
 769
 770
 771
 772
 773
 774
 775
 776
 777
 778
 779
 780
 781
 782
 783
 784
 785
 786
 787
 788
 789
 790
 791
 792
 793
 794
 795
 796
 797
 798
 799
 800
 801
 802
 803
 804
 805
 806
 807
 808
 809
 810
 811
 812
 813
 814
 815
 816
 817
 818
 819
 820
 821
 822
 823
 824
 825
 826
 827
 828
 829
 830
 831
 832
 833
 834
 835
 836
 837
 838
 839
 840
 841
 842
 843
 844
 845
 846
 847
 848
 849
 850
 851
 852
 853
 854
 855
 856
 857
 858
 859
 860
 861
 862
 863
 864
 865
 866
 867
 868
 869
 870
 871
 872
 873
 874
 875
 876
 877
 878
 879
 880
 881
 882
 883
 884
 885
 886
 887
 888
 889
 890
 891
 892
 893
 894
 895
 896
 897
 898
 899
 900
 901
 902
 903
 904
 905
 906
 907
 908
 909
 910
 911
 912
 913
 914
 915
 916
 917
 918
 919
 920
 921
 922
 923
 924
 925
 926
 927
 928
 929
 930
 931
 932
 933
 934
 935
 936
 937
 938
 939
 940
 941
 942
 943
 944
 945
 946
 947
 948
 949
 950
 951
 952
 953
 954
 955
 956
 957
 958
 959
 960
 961
 962
 963
 964
 965
 966
 967
 968
 969
 970
 971
 972
 973
 974
 975
 976
 977
 978
 979
 980
 981
 982
 983
 984
 985
 986
 987
 988
 989
 990
 991
 992
 993
 994
 995
 996
 997
 998
 999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<meta name="generator" content="SciTE" />
<meta http-equiv="Content-Type" content="text/html" />
<title>
SciTE
</title>
<style type="text/css">
table {
border: 1px solid #1F1F1F;
border-collapse: collapse;
}
td {
border: 1px solid #1F1F1F;
padding: 1px 5px 1px 5px;
}
th {
border: 1px solid #1F1F1F;
padding: 1px 5px 1px 5px;
}
.windowsonly {
background: #EBF3FF;
}
.gtkonly {
background: #FFFFE7;
}
.osxonly {
background: #FFE7E7;
}
.windows-osx {
background: #FFF3FF;
}
.example {
color: #008000;
font-weight: bold;
}
DIV.example {
background: #F7FCF7;
border: 1px solid #C0D7C0;
margin: 0.3em 3em;
padding: 0.3em 0.6em;
font-size: 80%;
}
h3 {
border: 2px solid #FFCC00;
background-color: #FFF7EE;
padding: 2px 5px;
}
.header{
border: 1px solid #CCCCCC;
}
.headerlinks {
padding: 7px;
background-color: #CCCCCC;
border: 0px solid #FF0000;
font-size: 120%;
}
</style>
</head>
<body bgcolor="#FFFFFF" text="#000000">
<table bgcolor="#000000" width="100%" cellspacing="0" cellpadding="0" style="border:0px solid #FF0000" border="0" summary="banner">
<tr>
<td>
<img src="SciTEIco.png" border="3" height="64" width="64" alt="Scintilla icon" />
</td>
<td>
<a href="index.html" style="color:white;text-decoration:none"><font size="5">
SciTE Documentation</font></a>
</td>
</tr>
</table>
<table class="header" width="100%" summary="header">
<tr>
<td class="headerlinks">
<a href="SciTEFAQ.html">
Frequently Asked Questions</a>&nbsp;&nbsp;
<a href="SciTELua.html">
Scripting</a>&nbsp;&nbsp;
<a href="SciTERegEx.html">Regular Expressions</a>&nbsp;&nbsp;
</td>
</tr>
</table>
<h3 id="StandardEditing">
Standard Editing
</h3>
<p>
Text editing in SciTE works similarly to most Macintosh or Windows editors with the added
feature of automatic syntax styling. SciTE can hold multiple files in memory at one time but
only one file will be visible. Rectangular
blocks of text can be selected in SciTE by holding down the Alt key on Windows or the Ctrl
key on GTK+ while dragging the mouse over the text. The modifier key used on GTK+
can be changed with the rectangular.selection.modifier property.
</p>
<p>
There are two panes in SciTE, the editing pane and the output pane. The output pane is
located either to the right of the editing pane or below it. Initially it is of zero size, but
it can be made larger by dragging the divider between it and the editing pane. The Options |
Vertical Split command can be used to move the output pane beneath the editing pane.
</p>
<p>
SciTE can perform commands to compile or run source files with the output from these
commands directed into the output pane.
</p>
<p>
For example, if <a href="http://www.python.org">Python</a> is installed on the machine, open
a new document, type:
</p>
<blockquote>
<kbd>
print "Hi"
</kbd>
</blockquote>
<p>
as that document's text.
</p>
Save the document as printhi.py. <br />
The document should now appear coloured as SciTE is using the file's extension to decide upon
the syntax styling to use:
<blockquote>
<code>
<b><font color="#000080">print </font></b>
<i><font color="#800080">"hi"</font></i>
</code>
</blockquote>
Perform the Tools | Go command.<br />
The output window will be made visible if it is not already visible and will show:<br />
<blockquote>
<code>
<font color="#0000FF">&gt;python -u printhi.py</font><br />
hi<br />
<font color="#0000FF">&gt;Exit code: 0</font>
</code>
</blockquote>
The first blue line is from SciTE showing the command it will use to run the program. The black
line is the output from running the Python program. The last blue line is from SciTE showing
that the program has finished and displaying its exit code. An exit code of zero indicates a
successful run. <br />
<p>
SciTE partially understands the error messages produced by Python, GCC, Visual C++, Borland
C++, PHP and other tools which use the same format as one of these. To see this, add a mistake to
the Python file by adding a second line to make the file:
</p>
<blockquote>
<code>
<span style="color:#000080;font-weight:bold;">print </span>
<span style="color:#800080;font-style:italic;">"hi"</span><br />
mistake
</code>
</blockquote>
<p>
Perform the Tools | Go command. The results should look like:
</p>
<blockquote>
<pre>
<span style="color:#0000FF">&gt;python -u printhi.py</span>
hi
Traceback (innermost last):
<span style="color:#FF0000">File "printhi.py", line 2, in ?</span>
mistake
NameError: mistake
<span style="color:#0000FF">&gt;Exit code: 1</span>
</pre>
</blockquote>
<p>
While it is easy to see where the problem is in this simple case, when a file is larger the
Tools | Next Message command can be used to view each of the reported errors. Upon performing
Tools | Next Message, the first error message in the output pane is highlighted with a yellow
background, and an error indicator is displayed for the appropriate line in the editing pane.
The caret is moved to this line and the pane is scrolled if needed to show the line. SciTE
now looks like this:
</p>
<img src="PrintHi.png" alt="SciTE after running Python interpreter" />
<p>
SciTE understands both the file name and line number parts of error messages in most cases
so can open another file (such as a header file) if errors were caused by that file. This
feature may not work where the file name is complicated by containing spaces or ".."
</p>
<p>
If command execution has failed and is taking too long to complete then the Tools | Stop
Executing command can be used.
</p>
<h3 id="CommandSubsystem">
Command subsystem
</h3>
<p>
Tools can be executed in various modes by SciTE which are called "subsystems". Different
subsystems are supported on Windows, GTK+ and OS X. The default subsystem is 0.
</p>
<table class="windowsonly" cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead><tr><td colspan="3">Windows</td></tr></thead>
<tr><td>0</td><td>console</td><td>Command line programs<br/>Do not use for GUI programs as their windows will not be visible.</td></tr>
<tr><td>1</td><td>windows</td><td>Programs that create their own windows</td></tr>
<tr><td>2</td><td>shellexec</td><td>Run using ShellExecute<br />
A good way to open HTML files and
similar as it handles this similarly to a user opening the file from the shell.</td></tr>
<tr><td>3</td><td>lua<br />director</td><td>Internal extension or director extension</td></tr>
<tr><td>4</td><td>htmlhelp</td><td>Open in HtmlHelp program<br />
Two part command separated by ! with the first
part being the topic to search for and the second the name of the help file
</td></tr>
<tr><td>5</td><td>winhelp</td><td>Open with WinHelp function<br />
Two part command similar to subsystem 4</td></tr>
<tr><td>7</td><td>immediate</td><td>Internal script that is executed immediately instead of being queued.</td></tr>
</table>
<br />
<table class="gtkonly" cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead><tr><td colspan="3">GTK+ and OS X</td></tr></thead>
<tr><td>0</td><td>console</td><td>Execute tool and wait for it to finish</td></tr>
<tr><td>2</td><td>shellexec</td><td>Execute in background</td></tr>
<tr><td>3</td><td>lua<br />director</td><td>Internal extension or director extension</td></tr>
<tr><td>7</td><td>immediate</td><td>Internal script that is executed immediately instead of being queued.</td></tr>
</table>
<h3 id="CommandLineArguments">
Command line arguments
</h3>
<p>
Command line arguments to SciTE include file names, commands and properties.
Commands and properties are preceded by "-" and are differentiated by the use in
commands of ':' as the first character that is not '.' or alphabetic.
Properties use the syntax used in property set files and override any
properties set in property files. If there is no value given for a property, it is set to 1.
Double quotes may be placed around arguments that contain spaces but they must be
placed around the whole argument, not just around a file name, so "-open:x y.txt" works but
-open:"x y.txt" doesn't.
On Linux, the standard shell quoting is available.
The "-p" argument causes SciTE to print the file and then exit.
</p>
<p>
For <span class="windowsonly">Windows</span>:<br />
The command line arguments "-" and "--" (without the quotes) are special in that they read the
stdin stream into the last buffer ("-"), or the output pane ("--"))<br />
The command line argument "-@" (without the quotes) is special in that file names are read from stdin
and opened.<br />
<b>Note:</b> when reading stdin into the output pane, when the property split.vertical is 0, the
output pane is increased to its maximum height. When the property split.vertical is 1, the output pane is
increased to approximately half of the screen width.<br />
<b>Note:</b> If stdin is not redirected, these arguments are effectively ignored.
</p>
<div>
For example,</div>
<div class="example">
SciTE "-font.base=font:MS Gothic,size:11" -save.recent ScintillaGTK.cxx
</div>
<div>starts SciTE, opens ScintillaGTK.cxx, loads the recent file list, and uses
11 point MS Gothic as the base font.<br />
A group of properties can be saved as a property set file (with the extension
".properties") and the import command used on the command line:</div>
<div class="example">
SciTE "-import c:\os\web_work" SciTEDoc.html
</div>
<p>
A few commands are currently available although this will expand in the future.
These commands are available:</p>
<table cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead>
<tr><th>Command</th><th>Argument</th></tr>
</thead>
<tr><td>close:</td><td></td></tr>
<tr><td>cwd:</td><td>change working directory</td></tr>
<tr><td>find:</td><td>search text</td></tr>
<tr><td>goto:</td><td>line number[,column number]</td></tr>
<tr><td>open:</td><td>file name</td></tr>
<tr><td>loadsession:</td><td>file name</td></tr>
<tr><td>quit:</td><td></td></tr>
<tr><td>replaceall:</td><td>search text\000replacement text</td></tr>
<tr><td>saveas:</td><td>file name</td></tr>
</table>
<br />
Commands use C style escape sequences which include:
<table cellpadding="0" cellspacing="0" border="1" summary="Command line escape sequences">
<thead>
<tr><th>Escape Sequence</th><th>Meaning</th></tr>
</thead>
<tr><td>\\</td><td>backslash</td></tr>
<tr><td>\a</td><td>bell</td></tr>
<tr><td>\b</td><td>backspace</td></tr>
<tr><td>\f</td><td>form feed</td></tr>
<tr><td>\n</td><td>new line</td></tr>
<tr><td>\r</td><td>carriage return</td></tr>
<tr><td>\t</td><td>tab</td></tr>
<tr><td>\v</td><td>vertical tab</td></tr>
<tr><td>\&lt;ooo&gt;</td><td>octal number specified by 1, 2, or 3 digits</td></tr>
<tr><td>\x&lt;hh&gt;</td><td>hexadecimal number specified by 2 digits</td></tr>
</table>
The following opens /big/icon.txt:<br />
<div class="example">
SciTE -open:/big/icon.txt
</div>
On Windows, the following opens C:\Program Files\SciTE\SciTEDoc.html
and goes to the 123rd line:<br />
<div class="example">
SciTE "-open:C:\\Program Files\\SciTE\\SciTEDoc.html" -goto:123
</div>
<p>
Command line arguments are evaluated left to right in two phases because
opening files requires the user interface to be available and there is also a need
to set some user interface properties before the user interface is displayed.
The first phase process arguments until just before the first file name would be opened.
The second phase processes the remaining arguments.
</p>
<p>
So, if you need to perform e.g. a find: or a goto: command on a file, you must put
the command after the filename, to allow SciTE to open the file before performing the command.
</p>
<p>
For <span class="windowsonly">Windows</span>:<br />
If any simple file name on the command line matches a directory name, the file open dialog appears - this is dependant upon the property
"open.dialog.in.file.directory"<br /><br />
If the property "buffers" is greater than one and the file name matches either a existing file or by means of a wildcard search, one or more files, the
matching files are loaded up to the property "buffers" count. Directories are not considered a match in this case<br /><br />
If the file name is an extension, optionally preceded by a path, and no such simple file name exists, the file open dialog appears, with the given extension as
the filter.<br /><br />
If the file name contains no extension, the property "source.default.extensions" is used to provide default extensions to attempt to match the file name to an
existing file.
</p>
<h3 id="Buffers">
Buffers
</h3>
<p>
SciTE may be configured to use between 1 and 100 buffers each containing a
file. The default is 1 and this effectively turns off buffers. With more than one buffer,
the Buffers menu can be used to switch between buffers, either by selecting the
file name or using the Previous (F6) and Next (Shift+F6) commands.
A tab is displayed for each buffer in the tab bar although this can be turned off with the
View | Tab Bar command.
A tab may be closed by clicking on it with the middle mouse button.
Setting large numbers of buffers may cause problems as some menus are fixed in length
and thus files beyond that length may not be accessible.
</p>
<p>
When all the buffers contain files, then opening a new file causes a buffer to be reused
which may require a file to be saved. In this case an alert is displayed to ensure the user
wants the file saved.
</p>
<h3 id="Sessions">
Sessions
</h3>
<p>
A session is a list of file names. You can save a complete set of your
currently opened buffers as a session for fast batch-loading in the
future.
Sessions are stored as properties files with the extension ".session".
</p>
<p>
Use File | Load Session and File | Save Session to load/save sessions.
You can turn on/off "last session autoloading" using SciTE properties
variable "save.session".
</p>
<p>
If "buffers" variable is set to "0" session management is turned off.
</p>
<p>
Loading previously saved session will close your currently opened
buffers. However you will not lose your edits, because you will be
asked to save unsaved buffers first.
</p>
<p>
Opening a specific file from command line overrides "save.session"
variable state. When you start SciTE loading a specific file from
command line last session will not restore even if "save.session"
variable is set to "1". This makes "save.session" safe to use - you
will never open a couple of files when you are trying to open just
one, specific file.
</p>
<p>
By setting "session.bookmarks" and "session.folds" variables bookmarks
and folding states of the currently opened buffers are saved in session
files and restored when sessions are loaded.
</p>
<h3 id="Languages">
Languages understood by SciTE
</h3>
<p>
SciTE currently is able to syntax style these languages (* denotes
support for folding):
</p>
<ul>
<li>Abaqus*</li>
<li>Ada</li>
<li>ANS.1 MIB definition files*</li>
<li>APDL</li>
<li>Assembler (NASM, MASM)</li>
<li>Asymptote*</li>
<li>AutoIt*</li>
<li>Avenue*</li>
<li>Batch files (MS-DOS)</li>
<li>Baan*</li>
<li>Bash*</li>
<li>BlitzBasic*</li>
<li>Bullant*</li>
<li>C/C++/C#*</li>
<li>Clarion*</li>
<li>cmake*</li>
<li>conf (Apache)*</li>
<li>CSound*</li>
<li>CSS*</li>
<li>D</li>
<li>diff files*</li>
<li>E-Script*</li>
<li>Eiffel*</li>
<li>Erlang*</li>
<li>Flagship (Clipper / XBase)*</li>
<li>Flash (ActionScript)*</li>
<li>Fortran*</li>
<li>Forth*</li>
<li>GAP*</li>
<li>Gettext</li>
<li>Haskell</li>
<li>HTML*</li>
<li>HTML with embedded JavaScript, VBScript, PHP and ASP*</li>
<li>Gui4Cli*</li>
<li>IDL - both MSIDL and XPIDL*</li>
<li>INI, properties* and similar</li>
<li>InnoSetup*</li>
<li>Java*</li>
<li>JavaScript*</li>
<li>LISP*</li>
<li>LOT*</li>
<li>Lout*</li>
<li>Lua*</li>
<li>Make</li>
<li>Matlab*</li>
<li>Metapost*</li>
<li>MMIXAL</li>
<li>MSSQL</li>
<li>nnCron</li>
<li>NSIS*</li>
<li>Objective Caml*</li>
<li>Opal</li>
<li>Octave*</li>
<li>Pascal/Delphi*</li>
<li>Perl, most of it except for some ambiguous cases*</li>
<li>PL/M*</li>
<li>Progress*</li>
<li>PostScript*</li>
<li>POV-Ray*</li>
<li>PowerBasic*</li>
<li>PowerShell*</li>
<li>PureBasic*</li>
<li>Python*</li>
<li>R*</li>
<li>Rebol*</li>
<li>Ruby*</li>
<li>Scheme*</li>
<li>scriptol*</li>
<li>Specman E*</li>
<li>Spice</li>
<li>Smalltalk</li>
<li>SQL and PLSQL</li>
<li>TADS3*</li>
<li>TeX and LaTeX</li>
<li>Tcl/Tk*</li>
<li>VB and VBScript*</li>
<li>Verilog*</li>
<li>VHDL*</li>
<li>XML*</li>
<li>YAML*</li>
</ul>
<p>
Running and building commands for some of these languages have been set up but should be
checked as they will have to be modified to work for many people.
</p>
<p>
To keep menus to a reasonable length some languages are included but have been commented
out in global options. These should be enabled by removing the comment character '#'.
</p>
<p>
Language settings are determined from the file extension but this can be changed
by selecting another language from the Language menu. The language menu can be
changed with the menu.language property.
</p>
<h3 id="FindReplace">
Find and Replace
</h3>
<p>
Either dialogs or strips may be used for find and replace, with dialogs being the default.
Strips are similar to find in web browsers, appearing at the bottom of the
window and are smaller and less distracting than dialogs.
They are specified with the find.use.strip and replace.use.strip properties.
</p>
<p>
SciTE has options to allow searching for words, regular expressions,
matching case, in the reverse direction, wrapping around the end of the
document.
C style backslash escapes which are listed in the command line
arguments section, may be used to search and replace control
characters.
Replacements can be made individually, over the current selection or
over the whole file. When regular expressions are used tagged
subexpressions can be used in the replacement text.
Regular expressions will not match across a line end.
</p>
<p>
SciTE supports
<a href="SciTERegEx.html">basic regular expressions</a>
with tagging.
</p>
<p>
On Windows, pressing Shift+Enter when the focus is in a text entry field will search
in the opposite of the current direction, so will normally search backwards.
</p>
<h3 id="Keyboard">
Keyboard commands
</h3>
<p>
Keyboard commands in SciTE mostly follow common Windows and GTK+ conventions.
All movement keys (arrows, page up/down, home and end)
allow to extend or reduce a stream selection when holding the Shift key,
and a rectangular selection when holding the Shift and Alt keys.
Some keys may not be available with some national keyboards or because
they are taken by the system such as by a window manager on GTK+.
The user.shortcuts setting may be used to assign a key to a function.
Note that Home key behaviour is changed by the vc.home.key option.
Keyboard equivalents of menu commands are listed in the menus.
Some less common commands with no menu equivalent are:
</p>
<table cellpadding="0" cellspacing="0" border="1" summary="Keyboard commands">
<tr>
<td>Magnify text size.</td><td>Ctrl+Keypad+</td>
</tr>
<tr>
<td>Reduce text size.</td><td>Ctrl+Keypad-</td>
</tr>
<tr>
<td>Restore text size to normal.</td><td>Ctrl+Keypad/</td>
</tr>
<tr>
<td>Cycle through recent files.</td><td>Ctrl+Tab</td>
</tr>
<tr>
<td>Indent block.</td><td>Tab</td>
</tr>
<tr>
<td>Dedent block.</td><td>Shift+Tab</td>
</tr>
<tr>
<td>Delete to start of word.</td><td>Ctrl+BackSpace</td>
</tr>
<tr>
<td>Delete to end of word.</td><td>Ctrl+Delete</td>
</tr>
<tr>
<td>Delete to start of line.</td><td>Ctrl+Shift+BackSpace</td>
</tr>
<tr>
<td>Delete to end of line.</td><td>Ctrl+Shift+Delete</td>
</tr>
<tr>
<td>Go to start of document.</td><td>Ctrl+Home</td>
</tr>
<tr>
<td>Extend selection to start of document.</td><td>Ctrl+Shift+Home</td>
</tr>
<tr>
<td>Go to start of display line.</td><td>Alt+Home</td>
</tr>
<tr>
<td>Go to end of document.</td><td>Ctrl+End</td>
</tr>
<tr>
<td>Extend selection to end of document.</td><td>Ctrl+Shift+End</td>
</tr>
<tr>
<td>Go to end of display line.</td><td>Alt+End</td>
</tr>
<tr>
<td>Expand or contract a fold point.</td><td>Ctrl+Keypad*</td>
</tr>
<tr>
<td>Select to next bookmark.</td><td>Alt+F2</td>
</tr>
<tr>
<td>Select to previous bookmark.</td><td>Alt+Shift+F2</td>
</tr>
<tr>
<td>Find selection.</td><td>Ctrl+F3</td>
</tr>
<tr>
<td>Find selection backwards.</td><td>Ctrl+Shift+F3</td>
</tr>
<tr>
<td>Scroll up.</td><td>Ctrl+Up</td>
</tr>
<tr>
<td>Scroll down.</td><td>Ctrl+Down</td>
</tr>
<tr>
<td>Line cut.</td><td>Ctrl+L</td>
</tr>
<tr>
<td>Line copy.</td><td>Ctrl+Shift+T</td>
</tr>
<tr>
<td>Line delete.</td><td>Ctrl+Shift+L</td>
</tr>
<tr>
<td>Line transpose with previous.</td><td>Ctrl+T</td>
</tr>
<tr>
<td>Selection duplicate.</td><td>Ctrl+D</td>
</tr>
<tr>
<td>Find matching preprocessor conditional, skipping nested ones.</td><td>Ctrl+K</td>
</tr>
<tr>
<td>Select to matching preprocessor conditional.</td><td>Ctrl+Shift+K</td>
</tr>
<tr>
<td>Find matching preprocessor conditional backwards, skipping nested ones.</td><td>Ctrl+J</td>
</tr>
<tr>
<td>Select to matching preprocessor conditional backwards.</td><td>Ctrl+Shift+J</td>
</tr>
<tr>
<td>Previous paragraph. Shift extends selection.</td><td>Ctrl+[</td>
</tr>
<tr>
<td>Next paragraph. Shift extends selection.</td><td>Ctrl+]</td>
</tr>
<tr>
<td>Previous word. Shift extends selection.</td><td>Ctrl+Left</td>
</tr>
<tr>
<td>Next word. Shift extends selection.</td><td>Ctrl+Right</td>
</tr>
<tr>
<td>Previous word part. Shift extends selection</td><td>Ctrl+/</td>
</tr>
<tr>
<td>Next word part. Shift extends selection.</td><td>Ctrl+\</td>
</tr>
<tr>
<td>Rectangular block selection.</td><td>Alt+Shift+Movement</td>
</tr>
<tr>
<td>Extend rectangular selection to start of line.</td><td>Alt+Shift+Home</td>
</tr>
<tr>
<td>Extend rectangular selection to end of line.</td><td>Alt+Shift+End</td>
</tr>
</table>
<p class="windowsonly">
On Windows, a search can be performed in the opposite direction by
using Shift+Enter in the Find or Replace strips or dialogs.
</p>
<h3 id="Abbreviations">
Abbreviations
</h3>
<p>
To use an abbreviation, type it and use the Expand Abbreviation
command or the Ctrl+B key. The abbreviation is replaced by an
expansion defined in the Abbreviations file. You can open the
Abbreviations file with a command in the Options menu and
add abbreviations. There is a default abbreviations file but a different
abbreviations file can be set for particular file extensions.
</p>
<p>
Each line in the files looks like "abbreviation=expansion".<br />
The abbreviations names can have any character (except perhaps control chars,
surely for CR and LF), including high Ascii chars (accented chars).<br />
Names have properties files limits: they cannot start with sharp (#) or space or tab
(but can have spaces inside); and they cannot have '=' character inside.<br />
Abbreviations names are limited to 32 characters. It is probably enough for
<em>abbreviations</em>...<br />
</p>
<p>
An expansion may contain new line characters indicated by '\n' and
a caret position indicated by the '|' character. To include a literal '|'
character, use '||'.<br />
Some simple examples are included in the distributed Abbreviations file.<br />
When expanding, the names don't need to be separated from the previous text.
Ie. if you define '��' as '&amp;eacute;', you can expand it inside a word.<br />
When multiple abbreviation names match, the longest matching name will be expanded.
</p>
<h3 id="Folding">
Folding
</h3>
<p>
SciTE supports folding for many languages (see the list of languages
understood by SciTE for more information.) Fold points are based upon
indentation for Python and on counting braces for the other languages.
</p>
<p>
The fold point markers (in the fold margin) can be clicked to expand and
contract folds. Normal clicking does not alter the fold state of child fold
points; naturally the children are hidden when the parent fold is
contracted, but when the parent is expanded again, each child is still
folded or not, as before.
</p>
<p>
Ctrl+Click on a fold point toggles it and performs the same operation on
all children.
</p>
<p>
Shift+Click on a fold point does not toggle that fold, it expands all the
child folds.
</p>
<p>
Ctrl+Shift+Click in the fold margin expands or contracts all the top level
folds.
"Toggle all folds" in the View menu does the same; it toggles only
top-level folds.
</p>
<p>
Tip:
To open a large code block with all its children folded, fold it with
Ctrl+Click, then open it with a normal click. Then on opening a child fold,
you will see that the grandchild folds are still closed; if you want those
'grandchild' folds open, Shift+Click the child fold.
</p>
<h3 id="PropertiesFile">
Properties file
</h3>
<p>
Much of SciTE's behaviour can be changed by editing the properties files.
</p>
<p>
There are four properties files used:</p>
<ul>
<li>Local properties file called "SciTE.properties" which may be
present in the same directory as the file being edited.</li>
<li>Directory properties file called "SciTEDirectory.properties" which may be
present in the same or in a parent directory as the file being edited.</li>
<li>User properties file called "SciTEUser.properties" on Windows
and ".SciTEUser.properties" on GTK+</li>
<li>Global properties file called "SciTEGlobal.properties"</li>
</ul>
<p>
Settings in the local properties file override those in the directory properties file
which overrides those in the user properties file which override those
in the global properties files. Environment variables are also available as properties and these
are overridden by an explicit setting in one of the properties files.
</p>
<p>
The directory properties file can be used as project options file where user commands and
compile, build commands should work in the same manner in subdirectories of a project. The
benefit is that local properties files in subdirectories can be replaced by one properties file
which is located at the root of the project.
The evaluation of the directory properties file is disabled by default and must be enabled by
setting the variable properties.directory.enable to 1 in the user or global properties file.
</p>
<p>
The user properties file is intended for customisation by the user,
leaving the global properties file to contain the default options distributed with SciTE.
The main use of the local properties files is to change the effects of the
Compile, Build and Go commands for the files in a directory. For example, I use the javac
compiler from the Java Development Kit for most work, so SciTEGlobal.properties sets the
command for compiling .java files to "javac". If I want to use the jvc compiler for the files
in one directory, then the SciTE.properties file in that directory contains an entry setting
the command to "jvc".
</p>
<p>
On Windows, the global properties file is located in the directory of the executable.
The user properties file is looked for in the user profile directory as set in the
USERPROFILE environment variable, or in the directory of the executable if
USERPROFILE is not set.
For GTK+ the user properties file is found in the user's home directory and the global
properties in a directory set at build time - normally /usr/share/scite.
If the "SciTE_HOME" environment variable is set on either Windows or GTK+ then it is where
both the global and user properties files are found.
</p>
<p>
There are commands in the Options menu for opening each of the properties files.
</p>
<p>
The files are in approximately the same format as Java properties files which have a simple
text format. Lines that start with '#' or that are completely blank are comments. Other lines
are of the form
</p>
<p>
variable=value
</p>
<p>
For long values, a '\' character at the end of the line continues that value on the next
line. Space characters are significant so <span class="example">x&nbsp;=1</span> defines a variable called
"x&nbsp;".
Values may include the values of other variables by using $(variablename). There are
some variables set by the environment to access the name of the current file as well:
</p>
<table cellpadding="0" cellspacing="0" border="1" summary="Variables set by the environment for use in property files">
<thead>
<tr><th>Name</th><th>Meaning</th></tr>
</thead>
<tr id='property-FilePath'><td>FilePath</td><td>full path of the current file</td></tr>
<tr id='property-FileDir'><td>FileDir</td><td>directory of the current file without a trailing slash</td></tr>
<tr id='property-FileName'><td>FileName</td><td>base name of the current file</td></tr>
<tr id='property-FileExt'><td>FileExt</td><td>extension of the current file</td></tr>
<tr id='property-FileNameExt'><td>FileNameExt</td><td>$(FileName).$(FileExt)</td></tr>
<tr id='property-Language'><td>Language</td><td>name of the lexer used for the current file</td></tr>
<tr id='property-SessionPath'><td>SessionPath</td><td>full path of the current session</td></tr>
<tr id='property-CurrentSelection'><td>CurrentSelection</td><td>value of the currently selected text</td></tr>
<tr id='property-CurrentWord'><td>CurrentWord</td><td>value of word which the caret is within or near</td></tr>
<tr id='property-Replacements'><td>Replacements</td><td>number of replacements made by last Replace command</td></tr>
<tr id='property-SelectionStartColumn'><td>SelectionStartColumn</td><td>column where selection starts</td></tr>
<tr id='property-SelectionStartLine'><td>SelectionStartLine</td><td>line where selection starts</td></tr>
<tr id='property-SelectionEndColumn'><td>SelectionEndColumn</td><td>column where selection ends</td></tr>
<tr id='property-SelectionEndLine'><td>SelectionEndLine</td><td>line where selection ends</td></tr>
<tr id='property-CurrentMessage'><td>CurrentMessage</td><td>most recently selected output pane message</td></tr>
<tr id='property-SciteDefaultHome'><td>SciteDefaultHome</td><td>directory in which the Global Options file is found</td></tr>
<tr id='property-SciteUserHome'><td>SciteUserHome</td><td>directory in which the User Options file is found</td></tr>
<tr id='property-SciteDirectoryHome'><td>SciteDirectoryHome</td><td>directory in which the Directory Options file is found</td></tr>
<tr id='property-APIPath'><td>APIPath</td><td>list of full paths of API files from api.<i>filepattern</i></td></tr>
<tr id='property-AbbrevPath'><td>AbbrevPath</td><td>full path of abbreviations file</td></tr>
</table>
<p>
Some features use file name patterns to see which variable to use. For example, the lexer
variable can be specialised for a particular file, or a group of files based upon wildcard
matching so:<br />
<b>lexer.makefile=makefile</b> indicates that the lexer called "makefile" should be used on
files called "makefile".<br />
<b>lexer.*.cxx=cpp</b> indicates that the lexer called "cpp" should be used on files with a
"cxx" extension.<br />
Variable substitution is available on the left hand side of file pattern assignments and
look like this:<br />
<b>file.patterns.html=*.html;*.htm;*.asp;*.shtml</b><br />
<b>command.go.$(file.patterns.html)=file://$(FilePath)</b>
</p>
<p>
Wildcard matching only works where the wildcard is at the start of a file specification, so "*.mak" will match "proj.mak" but
"Makefile*" will not match "Makefile.in".
</p>
<p>
Properties files are not treated as having a particular encoding, however individual property values
may be treated as having an encoding. For file names, commands, and user interface text, this is
UTF-8 so it may be easier to edit properties files as UTF-8 by inserting a coding cookie as explained later.
Other properties may be treated as byte sequences (like word.characters.<i>filepattern</i>) or in an implicit
encoding (such as keywords.<i>filepattern</i> matching the document encoding) so that it may be better to
edit these settings using a non-UTF-8 encoding. Where both UTF-8 and non-UTF-8 values are wanted,
two files can be used with different encodings and an import statement to include one in the other.
</p>
<h3 id="ImportAndConditional">
Importing properties files and conditional logic
</h3>
<p>
<a name="property-import"></a>
The 'import' statement includes a properties file as if the text were
inline at that point. The imported properties file
must be in the same directory as the current file and a properties
extension is assumed. Therefore a "import Lua" statement in
c:\os\scite\bin\SciTEGlobal.properties will import
c:\os\scite\bin\Lua.properties.
</p>
<p>
All of the properties files in a directory can be imported with "import *".
This does not import generic properties files like user properties or abbreviations.
The set of files that are imported can be controlled with the imports.include and imports.exclude
properties.
</p>
<p>
<a name="property-if"></a>
The 'if' statement takes one argument which is a
symbol that may be defined earlier in this property set file or in a base
property set. If the symbol evaluates to '0' then the test fails. An empty
string or not present symbol evaluates to 0. Into the very top property set
is inserted one of 'PLAT_GTK' with value '1',
'PLAT_WIN' with value '1', or 'PLAT_MAC' with value '1'.
For both PLAT_GTK and PLAT_MAC, 'PLAT_UNIX' is inserted with value '1'.
If the test succeeds then following indented statements are executed. When a
non-indented statement is found the if clause is finished. Only simple set
statements are allowed in if clauses. The evaluation of if statements occurs
at read time, not at evaluation time.
</p>
<h3 id="Parameters">
Command parameters and prompting
</h3>
<p>
SciTE has 4 properties $(1) .. $(4) which can be used to run commands with
changeable parameters. To set the parameter values, use the View | Parameters
command to view the modeless Parameters dialog which shows the current values
of these parameters and allows setting new values. The accelerator keys for the main
window remain active while this dialog is displayed, so it can be used to rapidly run
a command several times with different parameters. Alternatively, a command can be
made to display the modal Parameters dialog when executed by starting the
command with a '*' which is otherwise ignored. If the modeless Parameters dialog is
already visible, then the '*' is ignored.
</p>
<h3 id="Encodings">
Encodings
</h3>
<p>
SciTE will automatically detect the encoding scheme used for Unicode files that
start with a Byte Order Mark (BOM).
The UTF-8 and UTF-16 encodings are recognised including both Little Endian and
Big Endian variants of UTF-16.
</p>
<p>
UTF-8 files will also be recognised when they contain a coding cookie on one of the
first two lines. A coding cookie looks similar to "coding: utf-8" ("coding" followed by ':'
or '=', optional whitespace, optional quote, "utf-8") and is normally contained in
a comment:</p>
<div class="example"># -*- coding: utf-8 -*-</div>
For XML there is a declaration:<br />
<div class="example">&lt;?xml version='1.0' encoding='utf-8'?&gt;</div>
<p>
For other encodings set the code.page and character.set properties.
</p>
<h3 id="DefinedVariables">
<a name="property-"></a>
Defined variables in properties files
</h3>
<p>
Some properties are only available on
<span class="windowsonly">Windows</span>,
<span class="gtkonly">GTK+</span>, or.
<span class="osxonly">OS X</span>.
</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Defined variables in property files">
<tr id='property-position.left'>
<td>
<a name='property-position.top'></a><a name='property-position.width'></a><a name='property-position.height'></a><a name='property-position.maximize'></a>
position.left<br />
position.top<br />
position.width<br />
position.height<br />
position.maximize
</td>
<td>
Set the initial window size and position. If these are omitted then the
environment's defaults are used. If the width or height are -1 or the
position.maximize property is set then the window is maximised.
</td>
</tr>
<tr class="windowsonly" id='property-position.tile'>
<td>
position.tile
</td>
<td>
If there is another copy of SciTE open, set the initial window position to be
with the left side at position.left + position.width so that most of the time
you can see both copies at once without overlap.
Works nicely if position.left set to 0 and position.width set to half of the
screen width.
</td>
</tr>
<tr id='property-buffers'>
<td>
buffers
</td>
<td>
Set to a number between 1 and 100 to configure that many buffers.
Values outside this range are clamped to be within the range.
The default is 1 which turns off UI features concerned with buffers.<br />
This value is read only once, early in the startup process and only from the
global and user properties files. So after changing it, restart SciTE to see the effect.
</td>
</tr>
<tr id='property-buffers.zorder.switching'>
<td>
buffers.zorder.switching
</td>
<td>
This setting chooses the ordering of buffer switching when Ctrl+Tab pressed.
Set to 1, the buffers are selected in the order of their previous selection otherwise
they are chosen based on the buffer number.
</td>
</tr>
<tr id='property-are.you.sure'>
<td>
<a name='property-are.you.sure.for.build'></a>
are.you.sure<br />
are.you.sure.for.build
</td>
<td>
The classic GUI question. Normally, when SciTE is about to close a file which has unsaved
edits it asks this annoying question. To turn off the question, set are.you.sure to 0 and
files will be automatically saved without bothering the user. To abandon edits to a file
use the New command. New always asks "Are you sure?" giving an opportunity to not save
the file.<br />
When running or building a file, its most likely that you want the file to be saved
first. To enable a confirmation dialog for performing Compile, Build or Go commands, set
are.you.sure.for.build=1.
</td>
</tr>
<tr id='property-save.all.for.build'>
<td>
save.all.for.build
</td>
<td>
SciTE normally saves the current buffer when performing a Compile, Build, or Go
command. To save all buffers set save.all.for.build=1
</td>
</tr>
<tr id='property-view.whitespace'>
<td>
<a name='property-view.indentation.whitespace'></a>
view.whitespace<br />
view.indentation.whitespace
</td>
<td>
Setting view.whitespace to 1 makes SciTE start up with whitespace visible.<br />
Setting view.indentation.whitespace to 0 hides visible whitespace inside indentation.
</td>
</tr>
<tr id='property-whitespace.fore'>
<td>
<a name='property-whitespace.back'></a>
whitespace.fore<br />
whitespace.back
</td>
<td>
Sets the colours used for displaying all visible whitespace, overriding any styling
applied by the lexer.
</td>
</tr>
<tr id='property-view.indentation.guides'>
<td>
<a name='property-view.indentation.examine'></a><a name='property-highlight.indentation.guides'></a>
view.indentation.guides<br />
view.indentation.examine<br />
view.indentation.examine.<i>filepattern</i><br />
highlight.indentation.guides
</td>
<td>
Setting view.indentation.guides to 1 displays dotted vertical lines within indentation white
space every indent.size columns.<br />
Setting view.indentation.examine to 1 to display guides within real indentation whitespace only,
2 according to the next non-empty line (good for Python) or 3 according to both the next and
previous non-empty lines (good for most languages).<br />
Setting highlight.indentation.guides to 1 highlights the indentation guide associated with a
brace when that brace is highlighted.
</td>
</tr>
<tr id='property-view.eol'>
<td>
view.eol
</td>
<td>
Setting this to 1 makes SciTE display the characters that make up line ends. This looks
similar to (CR), (LF), or (CR)(LF). This is useful when using files created on another
operating system with software that is picky about line ends.
</td>
</tr>
<tr id='property-eol.mode'>
<td>
eol.mode
</td>
<td>
The default EOL mode (characters that make up line ends)
depends on your platform.
You can overwrite this behaviour by setting the property to
<div class="example">
LF for UNIX and OS X format<br />
CR for Macintosh format prior to OS X<br />
CRLF for DOS/Windows format</div>
</td>
</tr>
<tr id='property-eol.auto'>
<td>
eol.auto
</td>
<td>
This setting overrides the eol.mode value and chooses the end of
line character sequence based on the current contents of the file
when it is opened. The line ending used the most in the file is chosen.
</td>
</tr>
<tr id='property-blank.margin.left'>
<td>
<a name='property-blank.margin.right'></a>
blank.margin.left<br />
blank.margin.right
</td>
<td>
There is a blank margin on both sides of the text. It is drawn in the background colour
of default text. This defaults to one pixel for both left and right sides but may be
altered with these settings.
</td>
</tr>
<tr id='property-margin.width'>
<td>
margin.width
</td>
<td>
Setting this to a number makes SciTE display a selection margin to the left of the text.
The value is the number of pixels wide the selection margin should be. Line markers are
displayed in the selection margin area.
</td>
</tr>
<tr class="windowsonly" id='property-full.screen.hides.menu'>
<td>
full.screen.hides.menu
</td>
<td>
Setting this to 1 hides the menu bar when the Full Screen command is used on
Windows.
On GTK+ the menu is always visible.
</td>
</tr>
<tr class="windowsonly" id='property-minimize.to.tray'>
<td>
minimize.to.tray
</td>
<td>
Setting this to 1 minimizes SciTE to the system tray rather than to the task bar.
</td>
</tr>
<tr id='property-line.margin.visible'>
<td>
<a name='property-line.margin.width'></a>
line.margin.visible<br />
line.margin.width
</td>
<td>
SciTE is able to display a column of line numbers to the left of the selection
margin. Setting line.margin.visible to 1 makes this column visible at startup.
The line.margin.width property controls how much space is reserved for the line
numbers, in terms of the number of digits that can be displayed. To specify that
the margin should expand if needed to accommodate larger line numbers, add a '+'
after the number of digits, e.g. <span class="example">line.margin.width=3+</span>.
</td>
</tr>
<tr id='property-tabbar.visible'>
<td>
tabbar.visible
</td>
<td>
Setting tabbar.visible to 1 makes the tab bar visible at start up.
The buffers property must be set to a value greater than 1 for this option to work.
</td>
</tr>
<tr id='property-tabbar.hide.one'>
<td>
tabbar.hide.one
</td>
<td>
Setting tabbar.hide.one to 1 hides the tab bar until there is more than one tab.
</td>
</tr>
<tr class="windowsonly" id='property-tabbar.multiline'>
<td>
tabbar.multiline
</td>
<td>
Setting tabbar.multiline uses multiple lines for the tab bar
</td>
</tr>
<tr id='property-toolbar.visible'>
<td>
toolbar.visible
</td>
<td>
Setting this to 1 makes the tool bar visible at start up.
</td>
</tr>
<tr class="gtkonly" id='property-toolbar.usestockicons'>
<td>
toolbar.usestockicons
</td>
<td>
SciTE has a built-in icon set for the toolbar, setting this to 1 makes
SciTE more integrated in the GNOME desktop by using the icons
provided by the current theme used in GNOME.
</td>
</tr>
<tr class="gtkonly" id='property-pathbar.visible'>
<td>
pathbar.visible
</td>
<td>
The path bar is a line of text under the tab bar showing the full path of the currently selected tab.
Setting pathbar.visible to 1 makes the path bar visible on GTK+.
</td>
</tr>
<tr id='property-undo.redo.lazy'>
<td>
undo.redo.lazy
</td>
<td>
Setting this to 1 changes the technique used to determine when to enable or disable
tool bar buttons to be less accurate. This may improve performance on slow machines.
</td>
</tr>
<tr id='property-statusbar.visible'>
<td>
statusbar.visible
</td>
<td>
Setting this to 1 makes the status bar visible at start up.
</td>
</tr>
<tr id='property-statusbar.number'>
<td>
<a name='property-statusbar.text'></a>
statusbar.number<br />
statusbar.text.<i>number</i>
</td>
<td>
The statusbar.text.1 option defines the information displayed in the status bar
by default on all platforms.
Property values may be used in this text using the $() syntax.
Commonly used properties are: ReadOnly, EOLMode, BufferLength,
NbOfLines (in buffer), SelLength (chars), SelHeight (lines).
Extra properties defined for the status bar are LineNumber, ColumnNumber, and
OverType which is either "OVR" or "INS" depending on the overtype status.
You can also use file properties, which, unlike those above, are not updated
on each keystroke: FileName or FileNameExt, FileDate and FileTime and
FileAttr. Plus CurrentDate and CurrentTime.<br />
On Windows only, further texts may be set as statusbar.text.2 .. and these may be
cycled between by clicking the status bar.<br />
The statusbar.number option defines how many texts are to be cycled through.
</td>
</tr>
<tr id='property-buffered.draw'>
<td>
buffered.draw
</td>
<td>
Setting this to 0 rather than the default 1 makes SciTE draw output directly to the
screen rather than into a buffer bitmap first and then to the screen. Buffered drawing
flickers less but is slower.
</td>
</tr>
<tr id='property-two.phase.draw'>
<td>
two.phase.draw
</td>
<td>
Two phase drawing is a better but slower way of drawing text.
In single phase drawing each run of characters in one style is drawn along with
its background.
If a character overhangs the end of a run, such as in "<i>V</i>_" where the
"<i>V</i>" is in a different style from the "_", then this can cause the right hand
side of the "<i>V</i>" to be overdrawn by the background of the "_" which
cuts it off. Two phase drawing
fixes this by drawing all the backgrounds first and then drawing the text in
transparent mode. Two phase drawing may flicker more than single phase
unless buffered drawing is on. The default is for drawing to be two phase.
</td>
</tr>
<tr class="windowsonly" id='property-technology'>
<td>
technology
</td>
<td>
On Windows Vista or newer, this can be set to 1 to use the Direct2D and DirectWrite APIs
for higher quality antialiased drawing. The default is 0.
</td>
</tr>
<tr id='property-load.on.activate'>
<td>
<a name='property-save.on.deactivate'></a>
load.on.activate<br />
save.on.deactivate
</td>
<td>
The load.on.activate property causes SciTE to check whether the current file has been
updated by another process whenever it is activated. This is useful when another editor
such as a WYSIWYG HTML editor, is being used in conjunction with SciTE.<br />
The save.on.deactivate property causes SciTE to save the file whenever the SciTE
application loses focus. This is useful when developing web pages and you want to often
check the appearance of the page in a browser.
</td>
</tr>
<tr id='property-are.you.sure.on.reload'>
<td>
are.you.sure.on.reload
</td>
<td>
When both this and load.on.activate are set to 1, SciTE will ask if you really want to
reload the modified file, giving you the chance to keep the file as it is. By default this
property is disabled, causing SciTE to reload the file without bothering you.
</td>
</tr>
<tr id='property-save.on.timer'>
<td>
save.on.timer
</td>
<td>
The save.on.timer property causes SciTE to save modified files whenever there have been no
modifications for the number of seconds specified by the property.
When set to 0, the default, this feature is disabled and files are not automatically saved.
</td>
</tr>
<tr id='property-reload.preserves.undo'>
<td>
reload.preserves.undo
</td>
<td>
When set to 1, reloading a file does not delete all the undo history. This is useful
when load.on.activate is used in conjunction with filter commands.
</td>
</tr>
<tr id='property-check.if.already.open'>
<td>
check.if.already.open
</td>
<td>
This option allows opening files in an existing instance of SciTE rather than
always opening a new instance.
When this option is set and SciTE is started, it checks to see if
there are any other instances of SciTE open. If there is, another
instance is asked to open the file and become active and the new
instance exits.
On Windows, the instance with the Options | Open Files Here
menu item checked opens the file.
On GTK+, an arbitrary instance opens the file.
</td>
</tr>
<tr id='property-read.only'>
<td>
read.only
</td>
<td>
When this option is set then opened documents are initially read only.
New files are not affected by this setting.
</td>
</tr>
<tr id='property-background.open.size'>
<td>
<a name='property-background.save.size'></a>
background.open.size<br />
background.save.size
</td>
<td>
This setting controls whether files are opened and saved without blocking the user interface
while they are being read or written.
Files larger than the given size in bytes will be read or written in the background while
smaller files will be read or written directly and SciTE will not respond until the file access is completed.
The default value is -1 allows background processing for all files.
For saving, the size used is the in-memory size in bytes which will differ from the on-disk size
when the UTF-16 encoding is used.
</td>
</tr>
<tr class="windowsonly" id='property-temp.files.sync.load'>
<td>
temp.files.sync.load
</td>
<td>
Files dropped on SciTE on Windows are normally opened asynchronously
as there may be a long list. However, files dragged from some applications
such as 7-Zip may only exist for a moment in the temporary directory and
be deleted once the drop has occurred.<br />
Setting this to 1 makes SciTE open dropped files in the temporary directory
immediately.
</td>
</tr>
<tr id='property-quit.on.close.last'>
<td>
quit.on.close.last
</td>
<td>
If this option is set, SciTE will close when its last buffer has been
closed, e.g. with File/Close. (By default, if this option is not set,
SciTE will remain open and will create a new blank document when its
last buffer is closed.)
</td>
</tr>
<tr id='property-highlight.current.word'>
<td>
highlight.current.word
</td>
<td>
When set to 1, all occurrences of the selected word are highlighted with the
colour defined by highlight.current.word.colour. By default, this option is disabled. (See indicators.alpha and indicators.under)
</td>
</tr>
<tr id='property-highlight.current.word.indicator'>
<td>
highlight.current.word.indicator
</td>
<td>
If set, defines the appearance of the current word highlight. This is a
<a href="#IndicatorProperty">structured property</a> with multiple attributes similar to:
<div class="example">
highlight.current.word.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80
</div>
</td>
</tr>
<tr id='property-highlight.current.word.colour'>
<td>
highlight.current.word.colour
</td>
<td>
The option highlight.current.word.colour defines the colour of highlight.
The default value is #A0A000.<br />
Overridden by highlight.current.word.indicator.
</td>
</tr>
<tr id='property-highlight.current.word.by.style'>
<td>
highlight.current.word.by.style
</td>
<td>
If the option highlight.current.word.by.style is set, then only words with the same style
are highlighted (e.g. if you select this word in a comment, then only occurrences of words in
comments are selected).
</td>
</tr>
<tr class="osxonly" id='property-spell.ignore'>
<td>
spell.ignore.<i>filepattern</i>
</td>
<td>
Specifies a list of words that should not be treated as spelling mistakes for a particular filepattern.
For example, in HTML, tag names that are not words are common so turn off the spelling highlight with:
<div class="example">
spell.ignore.*.html=br ul toc valign blockquote kbd thead tr th tbody colspan</div>
To turn spell checking completely off for a filepattern use the value *.
</td>
</tr>
<tr class="osxonly" id='property-spell.mistake.indicator'>
<td>
spell.mistake.indicator
</td>
<td>
If set, defines the appearance of spelling mistakes. This is a
<a href="#IndicatorProperty">structured property</a> with multiple attributes similar to:
<div class="example">
spell.mistake.indicator=style:squigglepixmap,colour:#FF0000
</div>
</td>
</tr>
<tr class="gtkonly" id='property-rectangular.selection.modifier'>
<td>
rectangular.selection.modifier
</td>
<td>
On GTK+, the modifier key used to make rectangular selections can be set with this
property. Valid options are 2 (Ctrl), 4 (Alt) or 8 (Super). Super is often assigned to the
Windows/Start key on Windows keyboards or the Command key on Mac keyboards.
<br />
Since the Alt key is often used by window managers to move windows, this will need to
be configured off to use the combination in SciTE. This can be done for Metacity using
gconf-editor to modify the /apps/metacity/general/mouse_button_modifier. A valid value here
is &lt;Super&gt;.
</td>
</tr>
<tr id='property-selection.fore'>
<td>
<a name='property-selection.back'></a><a name='property-selection.alpha'></a>
selection.fore<br />
selection.back<br />
selection.alpha
</td>
<td>
Sets the colours used for displaying selected text. If one of these is not set then that
attribute is not changed for the selection. The default is to show the selection by
changing the background to light grey and leaving the foreground the same as when it was
not selected. The translucency of the selection is set with selection.alpha with an alpha
of 256 turning translucency off.
</td>
</tr>
<tr id='property-caret.fore'>
<td>
caret.fore
</td>
<td>
Sets the colour used for the caret.
</td>
</tr>
<tr id='property-selection.additional.fore'>
<td>
<a name='property-selection.additional.back'></a><a name='property-selection.additional.alpha'></a>
selection.additional.fore<br />
selection.additional.back<br />
selection.additional.alpha
</td>
<td>
Similar to selection.fore, selection.back, selection.alpha.
Sets the colours used for displaying additional selections when multiple selections are
enabled or a rectangular selection is made.
</td>
</tr>
<tr id='property-caret.additional.blinks'>
<td>
caret.additional.blinks
</td>
<td>
Set whether all carets blink. 0 means only the main caret blinks. Default is 1.
</td>
</tr>
<tr id='property-caret.line.back'>
<td>
<a name='property-caret.line.back.alpha'></a>
caret.line.back<br />
caret.line.back.alpha
</td>
<td>
Sets the background colour and translucency used for line containing the caret.
Translucency ranges from 0 for completely transparent to 255 for opaque with
256 being opaque and not using translucent drawing code which may be slower.
</td>
</tr>
<tr id='property-caret.period'>
<td>
caret.period
</td>
<td>
Sets the rate at which the caret blinks. The value is the time in milliseconds that the
caret is visible before it is switched to invisible. It then stays invisible for the same
period before appearing again. A value of 0 stops the caret from blinking.
</td>
</tr>
<tr id='property-caret.width'>
<td>
caret.width
</td>
<td>
Sets the width of the caret in pixels. Only values of 1, 2, or 3 work.
</td>
</tr>
<tr id='property-selection.rectangular.switch.mouse'>
<td>
selection.rectangular.switch.mouse
</td>
<td>
Sets whether switching to rectangular selection mode while making a selection with the mouse is
allowed (1) or not (0). Default is 0.
</td>
</tr>
<tr id='property-selection.multiple'>
<td>
<a name='property-selection.additional.typing'></a>
selection.multiple<br />
selection.additional.typing
</td>
<td>
Set selection.multiple to make multiple selections with the mouse by holding down the Ctrl key.<br />
Set selection.additional.typing to 1. to allow typing, backspace and delete to affect all selections including each line
of rectangular selections. When set to 0, typing only affects the main selection.
</td>
</tr>
<tr id='property-virtual.space'>
<td>
virtual.space
</td>
<td>
Determines whether the caret can be moved into virtual space, that is, beyond the last character on a line.
Set to 1 to allow virtual space when making a rectangular selection, 2 to allow the arrow keys or a mouse
click to move the caret into virtual space, and 3 to allow both.
</td>
</tr>
<tr id='property-caret.policy.xslop'>
<td>
<a name='property-caret.policy.width'></a><a name='property-caret.policy.xstrict'></a><a name='property-caret.policy.xeven'></a><a name='property-caret.policy.xjumps'></a><a name='property-caret.policy.yslop'></a><a name='property-caret.policy.lines'></a><a name='property-caret.policy.ystrict'></a><a name='property-caret.policy.yeven'></a><a name='property-caret.policy.yjumps'></a>
caret.policy.xslop<br />
caret.policy.width<br />
caret.policy.xstrict<br />
caret.policy.xeven<br />
caret.policy.xjumps<br /><br />
caret.policy.yslop<br />
caret.policy.lines<br />
caret.policy.ystrict<br />
caret.policy.yeven<br />
caret.policy.yjumps<br />
</td>
<td>
<p>If slop is set, we can define a slop value: width for xslop, lines for yslop.<br />
This value defines an unwanted zone (UZ) where the caret is... unwanted.<br />
This zone is defined as a number of pixels near the vertical margins,
and as a number of lines near the horizontal margins.<br />
By keeping the caret away from the edges, it is seen within its context,
so it is likely that the identifier that the caret is on can be completely seen,
and that the current line is seen with some of the lines following it which are
often dependent on that line.</p>
<p>If strict is set, the policy is enforced... strictly.<br />
The caret is centred on the display if slop is not set,
and cannot go in the UZ if slop is set.</p>
<p>If jumps is set, the display is moved more energetically
so the caret can move in the same direction longer before the policy is applied again.<br />
'3UZ' notation is used to indicate three time the size of the UZ as a distance to the margin.</p>
<p>If even is not set, instead of having symmetrical UZs,
the left and bottom UZs are extended up to right and top UZs respectively.<br />
This way, we favour the displaying of useful information: the begining of lines,
where most code reside, and the lines after the caret, e.g., the body of a function.</p>
<p>See the table below to see how these settings interact.<br />
Default: xslop, yslop, xeven, yeven=1, width=50, all others = 0.</p>
</td>
</tr>
<tr id='property-visible.policy.strict'>
<td>
<a name='property-visible.policy.slop'></a><a name='property-visible.policy.lines'></a>
visible.policy.strict<br />
visible.policy.slop<br />
visible.policy.lines
</td>
<td>
Determines how the display area is determined after a Go to command or
equivalent such as a Find or Next Message. Options are similar to caret.policy.*.
</td>
</tr>
<tr id='property-edge.mode'>
<td>
<a name='property-edge.column'></a><a name='property-edge.colour'></a>
edge.mode<br />
edge.column<br />
edge.colour<br />
</td>
<td>
Indicates long lines. The default edge.mode, 0, does not indicate long lines. An
edge.mode of 1 uses a vertical line to indicate the specified column and an edge.mode of
2 changes the background colour of characters beyond that column. For proportional fonts,
an edge.mode of 2 is more useful than 1.
</td>
</tr>
<tr id='property-control.char.symbol'>
<td>
control.char.symbol
</td>
<td>
Sets the character to use to indicate control characters. If
not set, control characters are shown as mnemonics.
</td>
</tr>
<tr id='property-error.marker.fore'>
<td>
<a name='property-error.marker.back'></a>
error.marker.fore<br />
error.marker.back
</td>
<td>
The colours used to indicate error and warning lines in both the edit and output panes
are set with these two values.
If there is a margin on a pane then a symbol is displayed in the margin to indicate
the error message for the output pane or the line causing the error message for the edit pane.
The error.marker.back is used as the fill colour of the symbol and the error.marker.fore
as the outline colour. If there is no margin then the background to the line is set to the
error.marker.back colour.
</td>
</tr>
<tr id='property-error.inline'>
<td>
<a name='property-style.error.0'></a><a name='property-style.error.1'></a><a name='property-style.error.2'></a><a name='property-style.error.3'></a>
error.inline<br />
style.error.0<br />
style.error.1<br />
style.error.2<br />
style.error.3
</td>
<td>
To see error messages interspersed with the source code, set error.inline=1.<br />
Different visual styles are used for different severities: style.error.0 is the default;
style.error.1 for warnings; style.error.2 for errors; and style.error.3 for fatal errors.
The severity of a message is inferred from finding the text "warning", "error", or "fatal" in the message.
</td>
</tr>
<tr id='property-bookmark.fore'>
<td>
<a name='property-bookmark.back'></a><a name='property-bookmark.alpha'></a>
bookmark.fore<br />
bookmark.back<br />
bookmark.alpha
</td>
<td>
The colours used to display bookmarks in the margin. If bookmark.fore is not set then
a blue sphere is used. When the margin is turned off, bookmarks are shown by a
change in the background colour of the line with the translucency set with bookmark.alpha.
</td>
</tr>
<tr id='property-find.mark.indicator'>
<td>
find.mark.indicator
</td>
<td>
If set, then the Mark All command in the Find dialog will draw indicators over
each string found. This is a
<a href="#IndicatorProperty">structured property</a> with multiple attributes similar to:
<div class="example">
find.mark.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80
</div>
</td>
</tr>
<tr id='property-find.mark'>
<td>
find.mark
</td>
<td>
If set, then the Mark All command in the Find dialog will draw translucent boxes over
each string found. (See indicators.alpha and indicators.under)<br />
Overridden by find.mark.indicator.
</td>
</tr>
<tr id='property-indicators.alpha'>
<td>
indicators.alpha
</td>
<td>
This property defines the alpha level for indicators (default value is 30).
The alpha value can range from 0 (completely transparent) to 255 (no transparency).
A value out of this range is ignored and the default one is used.<br />
Will be overridden by specific indicator definitions such as find.mark.indicator.
</td>
</tr>
<tr id='property-indicators.under'>
<td>
indicators.under
</td>
<td>
If set, the indicators are drawn under text or over (by default, it is over).<br />
Will be overridden by specific indicator definitions such as find.mark.indicator.
</td>
</tr>
<tr id='property-error.select.line'>
<td>
error.select.line
</td>
<td>
When a command execution produces error messages, and you step with F4 key through
the matching source lines, this option selects the line where the error occurs.
Most useful if the error message contains the column of error too as the selection will
start at the column of the error. The error message must contain the column and must be
understood by SciTE (currently only supported for HTML Tidy). The tab size assumed by
the external tool must match the tab size of your source file for correct column reporting.
</td>
</tr>
<tr id='property-openpath'>
<td>openpath.<i>filepattern</i></td>
<td>Defines a path for the Open Selected Filename command in the File
menu. The path is searched if the selected filename doesn't contain an
absolute path or the file is not found in the document directory. The
directories in openpath are separated by ';' on Windows and ':' on OS X and GTK+.<br />
An openpath setting may look like:
<div class="example">
openpath.*.txt=c:\dos\;f:\;<br />
openpath.$(file.patterns.cpp)=$(cpp_includes)</div>
</td>
</tr>
<tr id='property-open.suffix'>
<td>open.suffix.<i>filepattern</i></td>
<td>Defines a suffix to add to the selected file name for the
Open Selected Filename command in the File menu.
This is used in languages where the suffix is not given when accessing a file.
An example is python where "import xlib" will most often mean to import from
a file called "xlib.py".<br />
An open.suffix setting may look like:<br />
<div class="example">open.suffix.*.py=.py</div>
</td>
</tr>
<tr id='property-strip.trailing.spaces'>
<td>
strip.trailing.spaces<br />
strip.trailing.spaces.<i>filepattern</i>
</td>
<td>
Strips trailing white spaces from the file while saving.<br />
The global strip.trailing.spaces property can be overridden for
files that match a pattern by using the file pattern forms: <br />
<div class="example">
strip.trailing.spaces.*.yaml=0<br />
or <br />
strip.trailing.spaces.$(file.patterns.yaml)=0<br />
</div>
</td>
</tr>
<tr id='property-ensure.final.line.end'>
<td>
ensure.final.line.end
</td>
<td>
Ensures file ends with a line end when saved.
</td>
</tr>
<tr id='property-ensure.consistent.line.ends'>
<td>
ensure.consistent.line.ends
</td>
<td>
Ensures all lines end with the current Line End Characters setting when saved.
</td>
</tr>
<tr id='property-abbreviations'>
<td>
abbreviations.<i>filepattern</i>
</td>
<td>
Loads an abbreviations file for a particular language overriding the default abbreviations file.
For example,
<div class="example">
abbreviations.*.c=$(SciteUserHome)/c_abbrev.properties<br />
</div>
</td>
</tr>
<tr id='property-api'>
<td>
api.<i>filepattern</i>
</td>
<td>
Loads a set of API files for a particular language.
If there is more than one API file then the file names are separated by ';'.
API files contain a sorted list of
identifiers and function prototypes, one per line. If there are multiple files then each file should
end with a line end or the next file's first line will merge with the previous file's last line.
The "Complete Symbol" command
looks at the characters before the caret and displayed the subset of the API file
starting with that string. When an opening brace is typed, the file is searched for the
text preceding the caret and if a function prototype is found then it is displayed as a
calltip.
For example, the setting
<div class="example">
api.*.c=w.api<br />
</div>
could be used with a w.api file containing
<div class="example">
fclose(FILE* fileClose)<br />
FILE<br />
fopen(const char* szFileName, const char* szMode)<br />
fpos_t<br />
fread(void* buf, size_t size, size_t count, FILE* file)<br />
fseek(FILE* file, long lnOffset, int nOrigin)<br />
</div>
to provide autocompletion and calltips for some of the C file functions. It is best to
use the full path to the API file as otherwise the current directory is used.
See the Creating API files section for ways to create API files.
</td>
</tr>
<tr id='property-autocomplete.choose.single'>
<td>
autocomplete.choose.single
</td>
<td>
When set to 1 and an autocompletion list is invoked and there is only one element
in that list then that element is automatically chosen. This means that the matched
element is inserted and the list is not displayed.
</td>
</tr>
<tr id='property-autocomplete.*.ignorecase'>
<td>
autocomplete.<i>lexer</i>.ignorecase<br />
autocomplete.*.ignorecase
</td>
<td>
When set to 1 the API file is searched in a case insensitive way to find elements
for autocompletion lists. Otherwise matches only occur if case also matches.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-autocomplete.*.start.characters'>
<td>
autocomplete.<i>lexer</i>.start.characters<br />
autocomplete.*.start.characters
</td>
<td>
If this setting is not empty, typing any of the characters will cause
autocompletion to start. For example, if
autocomplete.python.start.characters=. and the API file for Python
contains "string.rjust" and "string.replace" then typing "string." will
cause the autocompletion to display both identifiers.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-autocomplete.*.fillups'>
<td>
autocomplete.<i>lexer</i>.fillups<br />
autocomplete.*.fillups
</td>
<td>
If this setting is not empty, typing any of the characters will cause
autocompletion to complete.
For example, if
autocomplete.python.fillups=( and the API file for Python
contains "string.replace" then typing "string.r(" will
cause "string.replace(" to be inserted.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-autocompleteword.automatic'>
<td>
autocompleteword.automatic
</td>
<td>
If this setting is 1 then when typing a word, if only one word in the document
starts with that string then an autocompletion list is displayed with that word so it
can be chosen by pressing Tab.
</td>
</tr>
<tr id='property-calltip.*.ignorecase'>
<td>
calltip.<i>lexer</i>.ignorecase<br />
calltip.*.ignorecase
</td>
<td>
When set to 1 the API file is searched in a case insensitive way to find the function
which will have its signature displayed as a calltip. The * form is used if there
is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.use.escapes'>
<td>
calltip.<i>lexer</i>.use.escapes<br />
calltip.*.use.escapes
</td>
<td>
When set to 1 the API file may contain C style backslash escapes which are listed in
the command line arguments section. The * form is used if there is no lexer specific
setting.
</td>
</tr>
<tr id='property-calltip.*.word.characters'>
<td>
calltip.<i>lexer</i>.word.characters<br />
calltip.*.word.characters
</td>
<td>
To determine the identifier to look up for calltips, a search is performed
allowing the characters in this set to be included in the identifier.
While the same setting can be used as for word.characters, sometimes
additional characters may be allowed.
For example, in Python, '.' is not normally considered part of a word
when selecting text, but it is good to allow "string.replace" to show a
calltip so calltip.python.word.characters=._$(chars.alpha) would be a
reasonable setting.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.parameters.start'>
<td>
<a name='property-calltip.*.parameters.end'></a><a name='property-calltip.*.parameters.separators'></a>
calltip.<i>lexer</i>.parameters.start<br />
calltip.<i>lexer</i>.parameters.end<br />
calltip.<i>lexer</i>.parameters.separators<br />
calltip.*.parameters.start<br />
calltip.*.parameters.end<br />
calltip.*.parameters.separators
</td>
<td>
Allows you to specify characters which start, end and separate
parameters. For most common languages, it's usually left brace for
start, right brace for end and comma or semicolon for separator.
E.g. CSS has colon for start, space for separator and nothing for
end. You can specify more characters for each property.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.end.definition'>
<td>
calltip.<i>lexer</i>.end.definition<br />
calltip.*.end.definition
</td>
<td>
API files may contain explanatory text after each function definition.
To display the explanation on a second line, set this property to the character used at the
end of the definition part. For most languages, this is ')'.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-xml.auto.close.tags'>
<td>
xml.auto.close.tags
</td>
<td>
For XML and HTML, setting this property to 1 will automatically insert the
corresponding end tag when '&gt;' is typed to end a start tag.
Type "&lt;td&gt;" and the result will be "&lt;td&gt;&lt;/td&gt;" with the caret
placed between the tags.
</td>
</tr>
<!--++Autogenerated - run ../scripts/RegenerateSource.py to regenerate -->
<!--**\(\*\n\) -->
<tr id='property-asp.default.language'>
<td>asp.default.language</td>
<td>Script in ASP code is initially assumed to be in JavaScript. To change this to VBScript set asp.default.language to 2. Python is 3.</td>
</tr>
<tr id='property-fold.asm.comment.explicit'>
<td>fold.asm.comment.explicit</td>
<td>This option enables folding explicit fold points when using the Asm lexer. Explicit fold points allows adding extra folding by placing a ;{ comment at the start and a ;} at the end of a section that should fold.</td>
</tr>
<tr id='property-fold.asm.comment.multiline'>
<td>fold.asm.comment.multiline</td>
<td>Set this property to 1 to enable folding multi-line comments.</td>
</tr>
<tr id='property-fold.asm.explicit.anywhere'>
<td>fold.asm.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.asm.explicit.end'>
<td>fold.asm.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard ;}.</td>
</tr>
<tr id='property-fold.asm.explicit.start'>
<td>fold.asm.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard ;{.</td>
</tr>
<tr id='property-fold.asm.syntax.based'>
<td>fold.asm.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.at.else'>
<td>fold.at.else</td>
<td>This option enables C++ folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-fold.basic.comment.explicit'>
<td>fold.basic.comment.explicit</td>
<td>This option enables folding explicit fold points when using the Basic lexer. Explicit fold points allows adding extra folding by placing a ;{ (BB/PB) or '{ (FB) comment at the start and a ;} (BB/PB) or '} (FB) at the end of a section that should be folded.</td>
</tr>
<tr id='property-fold.basic.explicit.anywhere'>
<td>fold.basic.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.basic.explicit.end'>
<td>fold.basic.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard ;} (BB/PB) or '} (FB).</td>
</tr>
<tr id='property-fold.basic.explicit.start'>
<td>fold.basic.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard ;{ (BB/PB) or '{ (FB).</td>
</tr>
<tr id='property-fold.basic.syntax.based'>
<td>fold.basic.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.comment'>
<td>fold.comment</td>
<td>This option enables folding multi-line comments and explicit fold points when using the C++ lexer. Explicit fold points allows adding extra folding by placing a //{ comment at the start and a //} at the end of a section that should fold.</td>
</tr>
<tr id='property-fold.cpp.comment.explicit'>
<td>fold.cpp.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.cpp.comment.multiline'>
<td>fold.cpp.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.cpp.explicit.anywhere'>
<td>fold.cpp.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.cpp.explicit.end'>
<td>fold.cpp.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.cpp.explicit.start'>
<td>fold.cpp.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.cpp.syntax.based'>
<td>fold.cpp.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.d.comment.explicit'>
<td>fold.d.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.d.comment.multiline'>
<td>fold.d.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.d.explicit.anywhere'>
<td>fold.d.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.d.explicit.end'>
<td>fold.d.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.d.explicit.start'>
<td>fold.d.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.d.syntax.based'>
<td>fold.d.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.haskell.imports'>
<td>fold.haskell.imports</td>
<td>Set to 1 to enable folding of import declarations</td>
</tr>
<tr id='property-fold.html'>
<td>fold.html</td>
<td>Folding is turned on or off for HTML and XML files with this option. The fold option must also be on for folding to occur.</td>
</tr>
<tr id='property-fold.html.preprocessor'>
<td>fold.html.preprocessor</td>
<td>Folding is turned on or off for scripts embedded in HTML files with this option. The default is on.</td>
</tr>
<tr id='property-fold.hypertext.comment'>
<td>fold.hypertext.comment</td>
<td>Allow folding for comments in scripts embedded in HTML. The default is off.</td>
</tr>
<tr id='property-fold.hypertext.heredoc'>
<td>fold.hypertext.heredoc</td>
<td>Allow folding for heredocs in scripts embedded in HTML. The default is off.</td>
</tr>
<tr id='property-fold.perl.at.else'>
<td>fold.perl.at.else</td>
<td>This option enables Perl folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-fold.perl.comment.explicit'>
<td>fold.perl.comment.explicit</td>
<td>Set to 0 to disable explicit folding.</td>
</tr>
<tr id='property-fold.perl.package'>
<td>fold.perl.package</td>
<td>Set to 0 to disable folding packages when using the Perl lexer.</td>
</tr>
<tr id='property-fold.perl.pod'>
<td>fold.perl.pod</td>
<td>Set to 0 to disable folding Pod blocks when using the Perl lexer.</td>
</tr>
<tr id='property-fold.preprocessor'>
<td>fold.preprocessor</td>
<td>This option enables folding preprocessor directives when using the C++ lexer. Includes C#'s explicit #region and #endregion folding directives.</td>
</tr>
<tr id='property-fold.quotes.python'>
<td>fold.quotes.python</td>
<td>This option enables folding multi-line quoted strings when using the Python lexer.</td>
</tr>
<tr id='property-fold.rust.comment.explicit'>
<td>fold.rust.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.rust.comment.multiline'>
<td>fold.rust.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.rust.explicit.anywhere'>
<td>fold.rust.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.rust.explicit.end'>
<td>fold.rust.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.rust.explicit.start'>
<td>fold.rust.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.rust.syntax.based'>
<td>fold.rust.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.sql.at.else'>
<td>fold.sql.at.else</td>
<td>This option enables SQL folding on a "ELSE" and "ELSIF" line of an IF statement.</td>
</tr>
<tr id='property-html.tags.case.sensitive'>
<td>html.tags.case.sensitive</td>
<td>For XML and HTML, setting this property to 1 will make tags match in a case sensitive way which is the expected behaviour for XML and XHTML.</td>
</tr>
<tr id='property-lexer.asm.comment.delimiter'>
<td>lexer.asm.comment.delimiter</td>
<td>Character used for COMMENT directive's delimiter, replacing the standard "~".</td>
</tr>
<tr id='property-lexer.cpp.allow.dollars'>
<td>lexer.cpp.allow.dollars</td>
<td>Set to 0 to disallow the '$' character in identifiers with the cpp lexer.</td>
</tr>
<tr id='property-lexer.cpp.hashquoted.strings'>
<td>lexer.cpp.hashquoted.strings</td>
<td>Set to 1 to enable highlighting of hash-quoted strings.</td>
</tr>
<tr id='property-lexer.cpp.track.preprocessor'>
<td>lexer.cpp.track.preprocessor</td>
<td>Set to 1 to interpret #if/#else/#endif to grey out code that is not active.</td>
</tr>
<tr id='property-lexer.cpp.triplequoted.strings'>
<td>lexer.cpp.triplequoted.strings</td>
<td>Set to 1 to enable highlighting of triple-quoted strings.</td>
</tr>
<tr id='property-lexer.cpp.update.preprocessor'>
<td>lexer.cpp.update.preprocessor</td>
<td>Set to 1 to update preprocessor definitions when #define found.</td>
</tr>
<tr id='property-lexer.css.hss.language'>
<td>lexer.css.hss.language</td>
<td>Set to 1 for HSS (.hss)</td>
</tr>
<tr id='property-lexer.css.less.language'>
<td>lexer.css.less.language</td>
<td>Set to 1 for Less CSS (.less)</td>
</tr>
<tr id='property-lexer.css.scss.language'>
<td>lexer.css.scss.language</td>
<td>Set to 1 for Sassy CSS (.scss)</td>
</tr>
<tr id='property-lexer.d.fold.at.else'>
<td>lexer.d.fold.at.else</td>
<td>This option enables D folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-lexer.errorlist.value.separate'>
<td>lexer.errorlist.value.separate</td>
<td>For lines in the output pane that are matches from Find in Files or GCC-style diagnostics, style the path and line number separately from the rest of the line with style 21 used for the rest of the line. This allows matched text to be more easily distinguished from its location.</td>
</tr>
<tr id='property-lexer.flagship.styling.within.preprocessor'>
<td>lexer.flagship.styling.within.preprocessor</td>
<td>For Harbour code, determines whether all preprocessor code is styled in the preprocessor style (0) or only from the initial # to the end of the command word(1, the default). It also determines how to present text, dump, and disabled code.</td>
</tr>
<tr id='property-lexer.haskell.allow.hash'>
<td>lexer.haskell.allow.hash</td>
<td>Set to 0 to disallow the '#' character at the end of identifiers and literals with the haskell lexer (GHC -XMagicHash extension)</td>
</tr>
<tr id='property-lexer.haskell.allow.questionmark'>
<td>lexer.haskell.allow.questionmark</td>
<td>Set to 1 to allow the '?' character at the start of identifiers with the haskell lexer (GHC & Hugs -XImplicitParams extension)</td>
</tr>
<tr id='property-lexer.haskell.allow.quotes'>
<td>lexer.haskell.allow.quotes</td>
<td>Set to 0 to disable highlighting of Template Haskell name quotations and promoted constructors (GHC -XTemplateHaskell and -XDataKinds extensions)</td>
</tr>
<tr id='property-lexer.haskell.cpp'>
<td>lexer.haskell.cpp</td>
<td>Set to 0 to disable C-preprocessor highlighting (-XCPP extension)</td>
</tr>
<tr id='property-lexer.haskell.import.safe'>
<td>lexer.haskell.import.safe</td>
<td>Set to 0 to disallow "safe" keyword in imports (GHC -XSafe, -XTrustworthy, -XUnsafe extensions)</td>
</tr>
<tr id='property-lexer.html.django'>
<td>lexer.html.django</td>
<td>Set to 1 to enable the django template language.</td>
</tr>
<tr id='property-lexer.html.mako'>
<td>lexer.html.mako</td>
<td>Set to 1 to enable the mako template language.</td>
</tr>
<tr id='property-lexer.props.allow.initial.spaces'>
<td>lexer.props.allow.initial.spaces</td>
<td>For properties files, set to 0 to style all lines that start with whitespace in the default style. This is not suitable for SciTE .properties files which use indentation for flow control but can be used for RFC2822 text where indentation is used for continuation lines.</td>
</tr>
<tr id='property-lexer.python.keywords2.no.sub.identifiers'>
<td>lexer.python.keywords2.no.sub.identifiers</td>
<td>When enabled, it will not style keywords2 items that are used as a sub-identifier. Example: when set, will not highlight "foo.open" when "open" is a keywords2 item.</td>
</tr>
<tr id='property-lexer.python.literals.binary'>
<td>lexer.python.literals.binary</td>
<td>Set to 0 to not recognise Python 3 binary and octal literals: 0b1011 0o712.</td>
</tr>
<tr id='property-lexer.python.strings.b'>
<td>lexer.python.strings.b</td>
<td>Set to 0 to not recognise Python 3 bytes literals b"x".</td>
</tr>
<tr id='property-lexer.python.strings.over.newline'>
<td>lexer.python.strings.over.newline</td>
<td>Set to 1 to allow strings to span newline characters.</td>
</tr>
<tr id='property-lexer.python.strings.u'>
<td>lexer.python.strings.u</td>
<td>Set to 0 to not recognise Python Unicode literals u"x" as used before Python 3.</td>
</tr>
<tr id='property-lexer.rust.fold.at.else'>
<td>lexer.rust.fold.at.else</td>
<td>This option enables Rust folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-lexer.sql.allow.dotted.word'>
<td>lexer.sql.allow.dotted.word</td>
<td>Set to 1 to colourise recognized words with dots (recommended for Oracle PL/SQL objects).</td>
</tr>
<tr id='property-lexer.sql.numbersign.comment'>
<td>lexer.sql.numbersign.comment</td>
<td>If "lexer.sql.numbersign.comment" property is set to 0 a line beginning with '#' will not be a comment.</td>
</tr>
<tr id='property-lexer.xml.allow.scripts'>
<td>lexer.xml.allow.scripts</td>
<td>Set to 0 to disable scripts in XML.</td>
</tr>
<tr id='property-sql.backslash.escapes'>
<td>sql.backslash.escapes</td>
<td>Enables backslash as an escape character in SQL.</td>
</tr>
<tr id='property-styling.within.preprocessor'>
<td>styling.within.preprocessor</td>
<td>For C++ code, determines whether all preprocessor code is styled in the preprocessor style (0, the default) or only from the initial # to the end of the command word(1).</td>
</tr>
<tr id='property-tab.timmy.whinge.level'>
<td>tab.timmy.whinge.level</td>
<td>For Python code, checks whether indenting is consistent. The default, 0 turns off indentation checking, 1 checks whether each line is potentially inconsistent with the previous line, 2 checks whether any space characters occur before a tab character in the indentation, 3 checks whether any spaces are in the indentation, and 4 checks for any tab characters in the indentation. 1 is a good level to use.</td>
</tr>
<!----Autogenerated -- end of automatically generated section -->
<tr id='property-user.shortcuts'>
<td>
user.shortcuts
</td>
<td>
Define keys that perform commands.
This is a '|' delimited list of keys and the commands they produce.
The commands are either <a href="CommandValues.html">string or numeric IDs</a>.
Numeric IDs above 2000 are Scintilla commands and are sent to the focussed pane.
Named IDs and numeric IDs below 2000 are SciTE menu commands.
The modifiers are Ctrl, Shift, and Alt and the named keys are Left,
Right, Up, Down, Insert, End, Home, Enter, Space, Tab, KeypadPlus, KeypadMinus,
KeypadMultiply, KeypadDivide, Escape, Delete, PageUp, PageDown, Slash,
Question, Equal, Win.
<br/>
<div class="example">
user.shortcuts=\<br/>
Ctrl+Shift+I|IDM_OPEN|\<br/>
Ctrl+Shift+Left|IDM_CLOSE|<br/>
</div>
This property is only read at start up.
<br/>
</td>
</tr>
<tr id='property-user.context.menu'>
<td>
user.context.menu
</td>
<td>
Define additional commands for the context menu.
This is a '|' delimited list of menu items and the commands they
produce with commands defined as in user.shortcuts. An empty
item produces a separator.
<br/>
<div class="example">
user.context.menu=\<br/>
||\<br/>
Next File|IDM_NEXTFILE|\<br/>
Prev File|IDM_PREVFILE|<br/>
</div>
</td>
</tr>
<tr id='property-magnification'>
<td>
<a name='property-output.magnification'></a>
magnification<br />
output.magnification
</td>
<td>
Sets the initial magnification factor of the edit and output panes. This is useful
when you want to change the size of text globally, such as after changing the
screen resolution without having to touch every style setting. 0 is default,
negative values makes the size smaller and positive values make it larger.
</td>
</tr>
<tr id='property-split.vertical'>
<td>
<a name='property-output.horizontal.size'></a><a name='property-output.vertical.size'></a><a name='property-output.initial.hide'></a>
split.vertical<br />
output.horizontal.size<br />
output.vertical.size<br />
output.initial.hide
</td>
<td>
If split.vertical is set to 1 then the output pane is to the right of the editing pane,
if set to 0 then the output pane is below the editing pane.
The output.*.size settings determine the initial size of the output pane.
If output.initial.hide is 1, then the output pane is hidden when SciTE first
starts up even when output.*.size is set; otherwise the output pane is shown at
startup.
</td>
</tr>
<tr id='property-clear.before.execute'>
<td>
clear.before.execute
</td>
<td>
If set to 1 then the output pane is cleared before any tool commands are run.
</td>
</tr>
<tr id='property-horizontal.scrollbar'>
<td>
<a name='property-horizontal.scroll.width'></a><a name='property-horizontal.scroll.width.tracking'></a><a name='property-output.horizontal.scrollbar'></a><a name='property-output.horizontal.scroll.width'></a><a name='property-output.horizontal.scroll.width.tracking'></a><a name='property-output.scroll'></a><a name='property-end.at.last.line'></a>
horizontal.scrollbar<br />
horizontal.scroll.width<br />
horizontal.scroll.width.tracking<br />
output.horizontal.scrollbar<br />
output.horizontal.scroll.width<br />
output.horizontal.scroll.width.tracking<br />
output.scroll<br />
end.at.last.line
</td>
<td>
If horizontal.scrollbar set to 0 then the edit pane's horizontal scrollbar is not displayed.<br />
horizontal.scroll.width is the document width assumed for scrolling.<br />
Similarly, output.horizontal.scrollbar and output.horizontal.scroll.width controls the
horizontal scroll bar of the output pane.<br />
The horizontal scroll bar widths can automatically grow as needed to ensure all displayed lines can be fully
scrolled with horizontal.scroll.width.tracking and output.horizontal.scroll.width.tracking.<br />
To stop the output pane from automatically scrolling, set output.scroll to 0.
To have the output pane scroll and return back to the line of the executed command,
set output.scroll to 1. If you want the output pane to scroll and remain at
the bottom after execution, set output.scroll to 2.<br />
The vertical scroll range is normally set so that maximum scroll position has
the last line at the bottom of the view. Set end.at.last.line to 0 to allow
scrolling one page below the last line.
</td>
</tr>
<tr id='property-wrap'>
<td>
<a name='property-output.wrap'></a>
wrap<br />
output.wrap
</td>
<td>
If wrap set to 1 then the edit pane is dynamically line wrapped.
If output.wrap set to 1 then the output pane is dynamically line wrapped.
These options have a high performance cost which is proportional to the amount of text
so should be turned off for large documents on slow machines.
</td>
</tr>
<tr id='property-wrap.style'>
<td>
wrap.style
</td>
<td>
Chooses between word wrapping (1, the default) and character wrapping (2).
Character wrapping is a better choice for Asian languages with no spaces
between words.
</td>
</tr>
<tr id='property-wrap.visual.flags'>
<td>
wrap.visual.flags
</td>
<td>
Flags to display markers at end and begin of wrapped lines for visual identify them.
Set to 0 to not display markers (default). Set to 1 to display markers at end of
wrapped lines, to 2 to display markers at begin of wrapped lines and to 3 to
display markers at begin and end.
</td>
</tr>
<tr id='property-wrap.visual.flags.location'>
<td>
wrap.visual.flags.location
</td>
<td>
Flags to set the location of the display markers (if enabled) near to text or near to border.
Set to 0 to have begin and end markers near to border (default). Set to 1 to
have end markers near text, to 2 to have begin markers near text and
to 3 to have all markers near text.
</td>
</tr>
<tr id='property-wrap.indent.mode'>
<td>
wrap.indent.mode
</td>
<td>
Wrapped sublines can be indented in various ways relative to the initial subline.
Default mode 0 indents sublines to the left of window plus wrap.visual.startindent.
Mode 1 aligns sublines to the first subline.
Mode 2 aligns sublines to the first subline plus one more level of indentation.
</td>
</tr>
<tr id='property-wrap.visual.startindent'>
<td>
wrap.visual.startindent
</td>
<td>
Sets the indention of continued wrapped lines to better visually identify the wrapping.
Default is 0 (no indention). Note if wrap.visual.flags is 2 or 3 (begin marker displayed)
the line is indented at least 1, even if wrap.visual.startindent is still 0.
</td>
</tr>
<tr id='property-wrap.aware.home.end.keys'>
<td>wrap.aware.home.end.keys</td>
<td>
This property changes the behaviour of the home and end keys when dynamic
line wrapping is turned on. When set to 0 (the default), the Home and End
keys will move the caret to the very beginning / end of the 'logical'
line, whether or not the line is wrapped over multiple lines in the display.
When this property is set to 1, the caret moves to the end of the current
'display' line if you press End once, or to the very end of the 'logical'
line if you press End again. Likewise, the Home key moves first to the
beginning of the 'display' line, then on to the very beginning of the line.
In a pane where dynamic line-wrapping is not enabled, this setting has no
effect.
</td>
</tr>
<tr id='property-cache.layout'>
<td>
<a name='property-output.cache.layout'></a>
cache.layout<br />
output.cache.layout
</td>
<td>
A large proportion of the time spent in the editor is used to lay out text prior
to drawing it. This information often stays static between repaints so can
be cached with these settings. There are four levels of caching. 0 is no caching,
1 caches the line that the caret is on, 2 caches the visible page as well as the caret,
and 3 caches the whole document. The more that is cached, the greater the
amount of memory used, with 3 using large amounts of memory, 7 times the
size of the text in the document. However,
level 3 dramatically speeds up dynamic wrapping by around 25 times on large
source files so is a very good option to use when wrapping is turned on and
memory is plentiful.
</td>
</tr>
<tr id='property-open.filter'>
<td>
open.filter
</td>
<td>
This is a complex expression used for determining the file types that will be available in
the open file dialog. For each type of file, there is some explanatory text, a '|'
character, some file patterns, and another '|' character. In the distributed
SciTEGlobal.properties file, the line continuation character '\', is used to spread these
items out, one per line. These file types appear in the "Files of type:" pull down. The
first item is the default, so you may wish to change the first item to include the file
types you commonly open.<br />
</td>
</tr>
<tr class="windowsonly" id='property-save.filter'>
<td>
save.filter
</td>
<td>
This is a complex expression used for determining the file types that will be available in
the save file dialog. The structure of the property is the same as open.filter.<br />
Does not work on GTK+.
</td>
</tr>
<tr id='property-max.file.size'>
<td>
max.file.size
</td>
<td>
To avoid accidentally loading huge files on slow media, or just to ensure SciTE is used
only to edit human readable code, the user can set the max.file.size property to specify
a limit to file loading.
If unset or set to 0, there is no limit.
If set to a given size in bytes and if a file to load exceeds this limit, the user is asked
if the file should be loaded. If accepted, the file is read as usual. If rejected then no
action is taken (no file loaded, no buffer created).
</td>
</tr>
<tr id='property-save.deletes.first'>
<td>
save.deletes.first
</td>
<td>
Causes files to be deleted before being opened for saving. Can be used
to ensure saving under a different capitalisation changes the files capitalisation rather
than silently using the old capitalisation.
</td>
</tr>
<tr id='property-save.check.modified.time'>
<td>
save.check.modified.time
</td>
<td>
With save.check.modified.time=1, when saving and the file has been modified by another
process, check if it should be overwritten by the current contents.
</td>
</tr>
<tr id='property-save.session'>
<td>
<a name='property-save.recent'></a><a name='property-save.position'></a>
save.session<br />
save.recent<br />
save.position<br />
save.find
</td>
<td>
If you set save.session, the list of currently opened buffers will be saved on exit
in a session file. When you start SciTE next time (without specifying a file name
on the command line) the last session will be restored automatically.<br />
For GTK+, the file is called ".SciTE.session" and is located in the directory
given by the SciTE_HOME environment variable and if that is not set, the value
of the HOME environment variable and if that is not set, the top level directory.
For Windows, the file is called "SciTE.session" and is located in the directory
given by the SciTE_HOME environment variable and if that is not set, the value
of the USERPROFILE environment variable and if that is not set, the directory
of the SciTE executable.<br />
Setting save.recent causes the most recently used files list to be saved on
exit in the session file and read at start up.<br />
Setting save.position causes the SciTE window position on the desktop to be
saved on exit in the session file and restored at start up.<br />
Setting save.find cause the "Find what" and "Replace with" to be saved in the session file.
</td>
</tr>
<tr id='property-session.bookmarks'>
<td>
<a name='property-session.folds'></a>
session.bookmarks<br />
session.folds
</td>
<td>
Setting session.bookmarks causes bookmarks to be saved in session files.
If you set session.folds then the folding state will be saved in session
files. When loading a session file bookmarks and/or folds are restored.
Folding states are not restored if fold.on.open is set.
</td>
</tr>
<tr class="windowsonly" id='property-open.dialog.in.file.directory'>
<td>
open.dialog.in.file.directory
</td>
<td>
Setting open.dialog.in.file.directory causes the open dialog to initially
display the same directory as the current file. If it is not set then the
system default is used.
</td>
</tr>
<tr class="windowsonly" id='property-find.close.on.find'>
<td>
find.close.on.find
</td>
<td>
Set to 0 to prevent the Find dialog from closing when "Find" pressed.
</td>
</tr>
<tr id='property-find.replace.matchcase'>
<td>
<a name='property-find.replace.regexp'></a><a name='property-find.replace.wrap'></a><a name='property-find.replace.escapes'></a>
find.replace.matchcase<br />
find.replace.regexp<br />
find.replace.wrap<br />
find.replace.escapes
</td>
<td>
These properties define the initial conditions for find and replace commands.
The find.replace.matchcase property turns of the "Match case" option,
find.replace.regexp the "Regular expression" option,
find.replace.wrap the "Wrap around" option and
find.replace.escapes the "Transform backslash expressions" option.<br />
</td>
</tr>
<tr class="windowsonly" id='property-find.replacewith.focus'>
<td>
find.replacewith.focus
</td>
<td>
If the find.replacewith.focus property is set, the Replace With input box is focused
in the Replace dialog if Find What is non-empty.
</td>
</tr>
<tr id='property-find.replace.regexp.posix'>
<td>
find.replace.regexp.posix
</td>
<td>
Change behaviour of Regular expression search.
If set to 0 (the default), characters '(' and ')' must be escaped by '\' to behave as regexp meta characters.
If set to 1, these characters are meta characters itself.
</td>
</tr>
<tr id='property-find.use.strip'>
<td>
<a name='property-replace.use.strip'></a>
find.use.strip<br />
replace.use.strip
</td>
<td>
Use in-window strips rather than dialogs for performing Find or Replace commands.
</td>
</tr>
<tr class="gtkonly" id='property-strip.button.height'>
<td>
strip.button.height
</td>
<td>
Buttons on GTK+ often contain extra spacing that makes strips take too much room.
This setting tries to limit the height of buttons.
A value of 23 or 24 may work well.
</td>
</tr>
<tr id='property-find.replace.advanced'>
<td>
find.replace.advanced
</td>
<td>
Enables Replace in Buffers command
<span class="windowsonly">and Search only in this style checkbox.
If enabled, searches can be restricted to a particular style (e.g. strings).</span>
</td>
</tr>
<tr class="osxonly" id='property-find.indicator'>
<td>
find.indicator
</td>
<td>
Controls the animated golden match indicator on OS X.
The default value, 1, shows and animates the find indicator then fades it away so surrounding text can be seen clearly.
Use the value 0 to disable the find indicator and the value 2 to keep the find indicator displayed.
This setting is not available on OS X 10.6.
</td>
</tr>
<tr id='property-find.command'>
<td>
find.command<br />
<span class="windowsonly">find.input</span>
</td>
<td>
The Find in Files command works in a similar way to the building commands executing a
command line tool with output redirected to the output pane. If the command produces
output understood by one of the error output passes, as does grep, then the F4 and
Shift+F4 keys can be used to move through all the matches. The $(find.what),
$(find.files), and $(find.directory) variables can be used for the values from the
Find in Files dialog.<br />
There are some scripts that implement this feature in Perl better than grep does
itself
<a href="http://jenda.krynicky.cz/#SciteFind">here</a> and
<a href="http://www.forusers.com/forme/finder.zip">here</a>.
This command line works with Cygwin on Windows, with modifications to suit
the Cygwin installation directory:<br />
<div class="example">
find.command=cmd /c c:\cygwin\bin\find "$(find.directory)"
-name "$(find.files)" -print0 |
c:\cygwin\bin\xargs -0 fgrep -G -n "$(find.what)"
</div>
On Windows, the find string can be given to the find command through
its standard input stream to avoid problems with quote interpretation.
To do this, specify find.input to be the search string, $(find.what).
<br />
If find.command is empty then SciTE's own search code is used. This only does a
simple search without regular expressions and is faster than running an external program.
</td>
</tr>
<tr id='property-find.files'>
<td>
find.files
</td>
<td>
This is the default set of files to search through using the Find in Files command.
The find.files property can contain a list of sets of files separated by '|' like
"*.cxx *.h|*.py *.pyw|*.html" which adds three entries to the history and
uses the first as the default value.<br />
The evaluation of this setting is a little unusual in that each entry in the value
from the property files is appended to the end of the history if that entry is
not already present. This means that opening files from different directories
will result in any local setting of find.files being added to the list.
</td>
</tr>
<tr id='property-find.in.dot'>
<td>
find.in.dot
</td>
<td>
If find.in.dot is 1 then Find in Files searches in directories that start with '.'.
The default behaviour is to prevent SciTE finding matches in the unmodified versions of
files kept by Subversion in .svn subdirectories.
</td>
</tr>
<tr id='property-find.in.binary'>
<td>
find.in.binary
</td>
<td>
If find.in.binary is 1 then Find in Files displays matches in binary files.
For Find in Files, a binary file is a file that contains a NUL byte in the first 64K block read from the file.
</td>
</tr>
<tr id='property-find.in.directory'>
<td>
find.in.directory
</td>
<td>
If set then Find in Files directory will be prefilled by this value.
If not set then Find in Files directory will be prefilled by directory of current file.
</td>
</tr>
<tr class="windowsonly" id='property-find.in.files.close.on.find'>
<td>
find.in.files.close.on.find
</td>
<td>
Set to 0 to prevent the Find in Files dialog from closing when "Find" pressed.
</td>
</tr>
<tr id='property-code.page'>
<td>
<a name='property-output.code.page'></a>
code.page<br />
output.code.page
</td>
<td>
To support a DBCS language such as Japanese, a code page can be set here. This ensures
that double byte characters are always treated as a unit so the caret is never located
between the two bytes of a double byte character.<br/><br/>
<table>
<thead><tr><th>Code page</th><th>Value</th></tr></thead>
<tr><td>Default (single byte character set)</td><td align="right">0</td></tr>
<tr><td>UTF-8</td><td align="right">65001</td></tr>
<tr><td>Japanese Shift-JIS</td><td align="right">932</td></tr>
<tr><td>Simplified Chinese GBK</td><td align="right">936</td></tr>
<tr><td>Korean Wansung</td><td align="right">949</td></tr>
<tr><td>Traditional Chinese Big5</td><td align="right">950</td></tr>
<tr><td>Korean Johab</td><td align="right">1361</td></tr>
</table>
Setting code.page to 65001 starts Unicode mode and the document is treated as
a sequence of characters expressed as UTF-8. Display is performed by converting to the
platform's normal Unicode encoding first so characters from any language will be displayed.
Correct glyphs may only be displayed if fonts are chosen that contain the appropriate glyphs.
The Tahoma font contains a wide range of glyphs so may be a good choice. <br/>
This property can <em>not</em> set a single byte character set.<br />
If output.code.page is set then it is used for the output pane which otherwise
matches the edit pane.
</td>
</tr>
<tr id='property-character.set'>
<td>
character.set
</td>
<td>
This setting allows changing the character set that is asked for when setting up fonts.
Not all of the values will work on all platforms.<br/><br/>
<table>
<thead><tr><th>Character set</th><th>Value</th></tr></thead>
<tr><td>Default</td><td align="right">0</td></tr>
<tr><td>Japanese</td><td align="right">128</td></tr>
<tr><td>Chinese GB2312</td><td align="right">134</td></tr>
<tr><td>Chinese BIG5</td><td align="right">136</td></tr>
<tr><td>Korean</td><td align="right">129</td></tr>
<tr><td>Greek</td><td align="right">161</td></tr>
<tr><td>Eastern European</td><td align="right">238</td></tr>
<tr class="windowsonly"><td>Baltic</td><td align="right">186</td></tr>
<tr class="windowsonly"><td>Turkish</td><td align="right">162</td></tr>
<tr><td>Hebrew</td><td align="right">177</td></tr>
<tr><td>Arabic</td><td align="right">178</td></tr>
<tr class="windowsonly"><td>Thai</td><td align="right">222</td></tr>
<tr class="windowsonly"><td>Vietnamese</td><td align="right">163</td></tr>
<tr><td>Cyrillic (CP1251 on Windows, KOI8-R on GTK+)</td><td align="right">204</td></tr>
<tr class="gtkonly"><td>Cyrillic (CP1251 on GTK+)</td><td align="right">1251</td></tr>
<tr class="gtkonly"><td>European with Euro (ISO 8859-15)</td><td align="right">1000</td></tr>
</table>
All of these values except for 1251 and 1000 should work on OS X or Windows.
On GTK+ Baltic, Turkish, Thai and Vietnamese will probably not work.
</td>
</tr>
<tr id='property-imports.include'>
<td>
<a name='property-imports.exclude'></a>
imports.include<br />
imports.exclude
</td>
<td>
These settings control which files are imported by import statements.<br/>
The imports.include property defines the names of the properties
files that may be imported. Say you are only interested in using
fortran and lisp, then in user properties, you could set<br />
<div class="example">
imports.include=fortran lisp
</div>
The imports.exclude property is examined only if imports.include is empty or missing.
This property stops the named files from being imported.
</td>
</tr>
<tr id='property-command.discover.properties'>
<td>
command.discover.properties
</td>
<td>
This property can be used to run a program to determine file encoding and other properties
when a file is loaded.<br />
The program should print a list of property=value lines for each property it wants to set.
This is the same format as properties files.<br />
<div class="example">
command.discover.properties=python /home/user/FileDetect.py "$(FilePath)"
</div>
A simple Python script that recognises a particular tag that indicates the file is in the Korean code page 949:<br />
<div class="example">
<span><span class="S5">import</span><span class="S0"> </span>sys<br />
<span class="S5">if</span><span class="S0"> </span><span class="S3">"Language:Korean"</span><span class="S0"> </span><span class="S5">in</span><span class="S0"> </span>open<span class="S10">(</span>sys<span class="S10">.</span>argv<span class="S10">[</span><span class="S2">1</span><span class="S10">]).</span>read<span class="S10">():</span><br />
<span class="S0">&nbsp; &nbsp; &nbsp; &nbsp; </span><span class="S5">print</span><span class="S10">(</span><span class="S4">'code.page=949'</span><span class="S10">)</span><br />
<span class="S0">&nbsp; &nbsp; &nbsp; &nbsp; </span><span class="S5">print</span><span class="S10">(</span><span class="S4">'character.set=129'</span><span class="S10">)</span><br />
<span class="S0"></span></span>
</div>
</td>
</tr>
<tr id='property-comment.block'>
<td>
<a name='property-comment.block.at.line.start'></a><a name='property-comment.stream.start'></a><a name='property-comment.stream.end'></a><a name='property-comment.box.start'></a><a name='property-comment.box.middle'></a><a name='property-comment.box.end'></a>
comment.block.<i>lexer</i><br />
comment.block.at.line.start.<i>lexer</i><br />
comment.stream.start.<i>lexer</i><br />
comment.stream.end.<i>lexer</i><br />
comment.box.start.<i>lexer</i><br />
comment.box.middle.<i>lexer</i><br />
comment.box.end.<i>lexer</i>
</td>
<td>
These settings are for the comment commands in the Edit menu and are
defined separately for each lexer. Not all languages support
both stream and block comments.<br />
Block comments are comments that start with a particular string and
continue until the end of line.
The comment.block property sets the string to be inserted or deleted
at the start of the selected lines when the Block Comment or Uncomment
command is performed. To make this command perform sensibly over
a range of text that already contains comments and other code, the string
can be defined to contain a character such as '~' that is not used in real
comments.<br />
Set comment.block.at.line.start to "1" to place block comment symbols
at the start of the lines, instead of just before the first non-blank
character of the lines.<br />
Stream comments start with a particular string and end with another
particular string and may continue over line ends. These are defined
with comment.stream.start and comment.stream.end. <br />
Box comments are a form of stream comment that takes several lines
and uses different strings for the start, end and other lines in the range.
These are defined with comment.box.start,
comment.box.middle and comment.box.end.
</td>
</tr>
<tr id='property-preprocessor.symbol'>
<td>
<a name='property-preprocessor.start'></a><a name='property-preprocessor.middle'></a><a name='property-preprocessor.end'></a>
preprocessor.symbol.<i>filepattern</i><br />
preprocessor.start.<i>filepattern</i><br />
preprocessor.middle.<i>filepattern</i><br />
preprocessor.end.<i>filepattern</i>
</td>
<td>
These settings make the preprocessor conditional movement and selection commands work.
The character that defines preprocessor lines is defined by preprocessor.symbol.
The preprocessor keywords that make up the start (if), middle (else), and end (endif)
of preprocessor conditionals are defined by the other three properties.
There may be multiple values for each of these, as, for example, C uses "if", "ifdef",
and "ifndef" to begin preprocessor conditionals.
</td>
</tr>
<tr id='property-lexer'>
<td>
lexer.<i>filepattern</i>
</td>
<td>
A lexer splits a file up into syntactic pieces. SciTE can then display these pieces in
different visual styles. Many lexers are included in SciTE for popular
programming languages such as Python, Java, C/C++, JavaScript and VB. Often several file
extensions (.cpp, .cc, .h) can map to one language (C++) and hence one lexer. These
settings associate a file name with a lexer.<br />
The lexers included in SciTE are written in C++ and compiled into the SciTE executable.
Lexers can also be written as a <a href="ScriptLexer.html">Lua script</a>
or as a Lua LPeg lexer using <a href="http://code.google.com/p/scintillua/">scintillua</a>.
</td>
</tr>
<tr id='property-shbang'>
<td>
shbang.<i>command</i>
</td>
<td>
On Unix, command files often have no extension and instead specify the interpreter
to use for the file in an initial line that starts with "#!". When the lexer can not be
otherwise determined and the file starts with "#!", the initial line is split up into words and
each word is prepended with "shbang.". If a property with this name exists then it is
treated as the extension of the file. For example, <span class="example">shbang.python=py</span> will be
triggered by an initial line <span class="example">#!/usr/bin/env python</span> so the file will be treated as Python.
</td>
</tr>
<tr id='property-lexerpath'>
<td>
lexerpath.<i>filepattern</i>
</td>
<td>
Specifies the path to an external lexer module that will be loaded into Scintilla.
</td>
</tr>
<tr id='property-keywords'>
<td>
<a name='property-keywords2'></a><a name='property-keywords3'></a><a name='property-keywords4'></a><a name='property-keywords5'></a><a name='property-keywords6'></a><a name='property-keywords7'></a><a name='property-keywords8'></a><a name='property-keywords9'></a><a name='property-keywordclass'></a>
keywords.<i>filepattern</i><br />
keywords2.<i>filepattern</i><br />
keywords3.<i>filepattern</i><br />
keywords4.<i>filepattern</i><br />
keywords5.<i>filepattern</i><br />
keywords6.<i>filepattern</i><br />
keywords7.<i>filepattern</i><br />
keywords8.<i>filepattern</i><br />
keywords9.<i>filepattern</i><br />
keywordclass.<i>lexer</i>
</td>
<td>
Most of the lexers differentiate between names and keywords and use the keywords
variables to do so. To avoid repeating the keyword list for each file extension, where
several file extensions are used for one language, a keywordclass variable is defined in
the distributed properties file although this is just a convention. Some lexers define a
second set of keywords which will be displayed in a different style to the first set of
keywords. This is used in the HTML lexer to display JavaScript keywords in a different
style to HTML tags and attributes.<br />
Keywords can be prefix based so ^GTK_ will treat all words that start
with GTK_ as keywords.
</td>
</tr>
<tr id='property-default.file.ext'>
<td>
default.file.ext
</td>
<td>
Defines the language mode used before the file has a name. For example, if
default.file.ext=.py, then when the New command is used to create a new file then Python
syntax styling is used.
</td>
</tr>
<tr id='property-word.characters'>
<td>
word.characters.<i>filepattern</i>
</td>
<td>
Defines which characters can be parts of words. The default value here is all the
alphabetic and numeric characters and the underscore which is a reasonable value for
languages such as C++.
</td>
</tr>
<tr id='property-whitespace.characters'>
<td>
whitespace.characters.<i>filepattern</i>
</td>
<td>
Defines which characters are considered whitespace. The default value is that initially set up
by Scintilla, which is space and all chars less than 0x20. Setting this property allows you to
force Scintilla to consider other characters as whitespace (e.g. punctuation) during such activities
as cursor navigation (ctrl+left/right).
</td>
</tr>
<tr id='property-style.*'>
<td>
style.*.<i>stylenumber</i><br />
style.<i>lexer</i>.<i>stylenumber</i>
</td>
<td>
The lexers determine a style number for each lexical type, such as keyword, comment or
number. These settings determine the visual style to be used for each style number of
each lexer.<br />
The value of each setting is a set of ',' separated fields, some of which have a
subvalue after a ':'. The fields are font, size, fore, back, italics, notitalics, bold,
notbold, weight, eolfilled, noteolfilled, underlined, notunderlined, and case.
The font field has a subvalue which is the name of
the font, the fore and back have colour subvalues,
the size field has a (fractional) numeric size subvalue,
the weight field has a numeric size subvalue (1.. 999: 100=light, 400=normal, 700=bold),
the case field has a subvalue of 'm', 'u', or 'l' for mixed, upper or lower case,
and the bold, italics and eolfilled fields have no subvalue. The value
"fore:#FF0000,font:Courier,size:14" represents 14 point, red Courier text.<br />
A global style can be set up using style.*.<i>stylenumber</i>. Any style options set in
the global style will be inherited by each lexer style unless overridden.<br />
On GTK+, the font name should be prefixed with "!" such as "font:!Sans" to ensure Pango
anti-aliased fonts are used. If this is not done, an older font system will be used which may not work well.
</td>
</tr>
<tr>
<td>
style.<i>lexer</i>.32<br />
style.<i>lexer</i>.33<br />
style.<i>lexer</i>.34<br />
style.<i>lexer</i>.35<br />
style.<i>lexer</i>.36<br />
style.<i>lexer</i>.37<br />
style.<i>lexer</i>.38
</td>
<td>
As well as the styles generated by the lexer, there are other numbered styles used.<br />
Style 32 is the default style and its features will be inherited by all other styles
unless overridden.<br />
Style 33 is used to display line numbers in the margin.<br />
Styles 34 and 35 are used to display matching and non-matching braces
respectively.<br />
Style 36 is used for displaying control characters. This is not a full style as the
foreground and background colours for control characters are determined by their lexical
state rather than this style.<br />
Style 37 is used for displaying indentation guides. Only the fore and back are used.<br />
Style 38 is used for displaying calltips. Only the font, size, fore and back are used.<br />
A * can be used instead of a lexer to indicate a global style setting.
</td>
</tr>
<tr class="windows-osx" id='property-font.quality'>
<td>
font.quality
</td>
<td>
This setting allows choosing different ways of drawing text on Windows and OS X.
The appearance will depend on platform settings and, on Windows, the technology setting.
This setting does not currently have any effect on GTK+.
<table>
<thead><tr><th>Value</th><th>Meaning</th></tr></thead>
<tr><td>0</td><td>Default</td></tr>
<tr><td>1</td><td>Non-antialiased</td></tr>
<tr><td>2</td><td>Antialiased</td></tr>
<tr><td>3</td><td>LCD Optimized</td></tr>
</table>
</td>
</tr>
<tr id='property-braces.check'>
<td>
<a name='property-braces.sloppy'></a>
braces.check<br />
braces.sloppy<br />
style.<i>lexer</i>.34<br />
style.<i>lexer</i>.35<br />
braces.<i>lexer</i>.style
</td>
<td>
Brace highlighting is a feature that shows the range of a brace when the caret is
positioned immediately after it. It is especially useful when complex nested braces are
used. The characters '(', ')', '[', ']', '{', and '}' are considered braces. The feature
defaults to off (because it slows cursor movement) unless braces.check is set to 1. If
braces.sloppy is set to 1 then if there is no brace before the caret then the character
after the caret is checked. The highlighting is performed by displaying the braces in
style number 34 or in style number 35 if there is no matching brace. While this is a full
style, to avoid partial display of the braces, it is best to make this style differ from
the standard style of braces only in foreground and background colour. Only braces with
style set to braces.<i>lexer</i>.style (which defaults to 0) are candidates for brace
match highlighting.
</td>
</tr>
<tr id='property-font.monospace'>
<td>
font.monospace
</td>
<td>
Defines, with the same syntax as the style properties,
the font name and size to be used when the Use Monospaced Font
command is performed.
</td>
</tr>
<tr id='property-command.compile'>
<td>
<a name='property-command.compile.subsystem'></a><a name='property-command.build'></a><a name='property-command.build.subsystem'></a><a name='property-command.build.directory'></a><a name='property-command.go'></a><a name='property-command.go.subsystem'></a>
command.compile.<i>filepattern</i><br />
command.compile.subsystem.<i>filepattern</i><br />
command.build.<i>filepattern</i><br />
command.build.subsystem.<i>filepattern</i><br />
command.build.directory.<i>filepattern</i><br />
command.go.<i>filepattern</i><br />
command.go.subsystem.<i>filepattern</i>
</td>
<td>
These settings choose which commands to execute when the Compile, Build or Go menu items
are selected. The subsystem options are explained in the subsystem section.<br />
When source files are in a different directory to that they should be built in, the
command.build.directory property can be set to change to a particular directory before performing
the build.
</td>
</tr>
<tr id='property-command.go.needs'>
<td>
<a name='property-command.go.needs.subsystem'></a>
command.go.needs.<i>filepattern</i><br />
command.go.needs.subsystem.<i>filepattern</i>
</td>
<td>
Sometimes a file must be compiled or built before it can be run. If this is the case,
this setting indicates what command needs to be run to perform the compile or build step
before running the file. When a file is compiled, this is noted and future runs will not
perform a compile or build. To make a 'compile and go' Go command for .c files:
<div class="example">
command.go.*.c=$(FileName)<br />
command.go.needs.*.c=g++ $(FileNameExt) -o $(FileName)<br />
</div>
</td>
</tr>
<tr>
<td>
command.name.<i>number</i>.<i>filepattern</i><br />
command.<i>number</i>.<i>filepattern</i><br />
command.is.filter.<i>number</i>.<i>filepattern</i><br />
command.subsystem.<i>number</i>.<i>filepattern</i><br />
command.save.before.<i>number</i>.<i>filepattern</i><br />
<span class="windowsonly">command.input.<i>number</i>.<i>filepattern</i></span><br />
command.replace.selection.<i>number</i>.<i>filepattern</i><br />
<span class="windowsonly">command.quiet.<i>number</i>.<i>filepattern</i></span><br />
command.mode.<i>number</i>.<i>filepattern</i><br />
command.shortcut.<i>number</i>.<i>filepattern</i>
</td>
<td>
Extra commands can be added to the Tools menu. For example to include the 'astyle'
indenter, the properties file could contain
<div class="example">command.name.0.*.cc=Indent<br />
command.0.*.cc=astyle -taO $(FileNameExt)<br />
command.is.filter.0.*.cc=1</div>
The first line defines the string that will appear in the Tools menu (immediately below
'Go'). The second line is the command string, similar to those of the compile, build, and
go commands. The optional command.is.filter property states that the command modifies the
current file so it may need to be read in after performing the command if
load.on.activate is set.<br />
If command.save.before is set to 1, SciTE automatically saves the file before execution.
If it is set to 2, SciTE will not save the file, otherwise SciTE asks you.
On Windows, the optional command.input property specifies text that will be piped
to the command. This may reference other properties; for example,
<span class="example">command.input.0.*.cc=$(CurrentSelection)</span>
would pipe the current selection to the command processes.
The command.input property is only supported for subsystem 0
(command line programs).<br />
<br />
The optional command.replace.selection can be used to specify that the
command output should replace the current selection (or be inserted at the cursor
location, if there is no selection). This property has three available settings:
0, the default, means do not replace the selection. 1 means replace the selection
when the command finishes. 2 means replace the selection only if the command
finishes with an exit code of 0. If the user cancels the command via "Tools / Stop
Executing", the selection will not be replaced even in mode 1. Note, commands run
asynchronously, so you are not prevented from modifying the document or even
switching buffers while a command is running. However, please bear in mind that
command.replace.selection will send the output to whatever window is active <i>when
the command completes</i>.<br />
A final command property that is currently supported only on windows is command.quiet.
A value of 1 indicates that the command I/O should not be echoed to the output pane.
This may be useful in combination with command.input and command.replace.selection.<br />
<br />
The command.mode property is a comma-separated list of flags / settings. Each mode
setting can have an argument, separated from the setting name by a colon. For
most of these, the argument portion is optional; if the setting name appears without
an argument, this works the same as "setting:yes". If a setting is included in
the command.mode but also appears as a separate command property, the mode property
will be overridden. Similarly, if a single setting appears more than once with
different arguments, the last valid argument takes priority. The supported
command.mode settings are:
<div class="example">
filter - accepts keyword arguments yes and no<br />
quiet - accepts keyword arguments yes and no<br />
replaceselection - accepts yes, no, and auto<br />
savebefore - accepts yes, no, and prompt<br />
subsystem - console, windows, shellexec, lua, director, winhelp, htmlhelp, immediate<br />
groupundo - yes or no
</div>
Currently, all of these except groupundo are based on individual properties with
similar names, and so are not described separately here. The groupundo setting
works with subsystem 3 (lua / director), and indicates that SciTE should treat any
changes made by the command as a single undo action. A command that uses the
groupundo setting should not change which buffer is active in the editor.<br />
The command.shortcut property allows you to specify a keyboard shortcut for the
command. By default, commands 0 to 9 have keyboard shortcuts Ctrl+0 to Ctrl+9
respectively, but this can be overridden. For commands numbered higher than 9,
there is no default keyboard shortcut. The notation used to specify keyboard
shortcuts is the same as for the user.shortcuts property, described elsewhere
in this document.<br />
<br />
If the text of a command starts with '*' then the Parameters dialog is displayed to
prompt for parameters before executing the command. The initial '*' is not included
in the command that is executed.<br />
<br />
The command number can be in the range of 0 to 49. Command numbers 0 to 9 are
assigned Ctrl+Number shortcuts. Internally these commands use IDs starting from
1100 (IDM_TOOLS) which can be used in user.shortcuts and user.context.menu as:
<div class="example">user.context.menu=Indent|1100|</div>
If command.name is empty then no item is added to the Tools menu. This can be used
for commands that are only in the context menu or user shortcuts.
</td>
</tr>
<tr id='property-command.help'>
<td>
<a name='property-command.help.subsystem'></a>
command.help.<i>filepattern</i><br />
command.help.subsystem.<i>filepattern</i>
</td>
<td>
Defines a command to be executed when the help command is
invoked or F1 pressed. On Windows, this often uses subsystem 4 as described above.
On OS X or Linux, running man or a browser are common ways of displaying help.
The word at the cursor is copied to $(CurrentWord) and this is often a good argument
to the help application. The subsystem property works in the same way as for other
commands.
</td>
</tr>
<tr id='property-command.scite.help'>
<td>
<a name='property-command.scite.help.subsystem'></a>
command.scite.help<br />
command.scite.help.subsystem
</td>
<td>
Defines a command to be executed for help on the SciTE program itself which normally
means displaying this file in a browser.
</td>
</tr>
<tr class="gtkonly" id='property-command.print'>
<td>
<a name='property-command.print.subsystem'></a>
command.print.<i>filepattern</i><br />
command.print.subsystem.<i>filepattern</i>
</td>
<td>
Defines a command to be executed when print is invoked on GTK+ 2.x.
On Windows and GTK+ 3.x, printing is performed directly by SciTE.
</td>
</tr>
<tr id='property-time.commands'>
<td>
time.commands
</td>
<td>
When a command is completed, print the time it took in seconds.
</td>
</tr>
<tr id='property-print.magnification'>
<td>
print.magnification
</td>
<td>
Printing is normally done with the same settings as screen display.
To make the printing larger or smaller, the print.magnification
setting is added to the size of every font when printed. To get a
good miniaturisation of text, set print.magnification to -4.
</td>
</tr>
<tr id='property-print.colour.mode'>
<td>
print.colour.mode
</td>
<td>
Some people prefer light coloured text on a black background on
screen but dark text on white on paper. If print.colour.mode is set
to 1 then each colour is inverted for printing. If set to 2 then
printing produces black text on white background. 3 forces the
background to white and 4 forces the default background to white.
</td>
</tr>
<tr class="windowsonly" id='property-print.margins'>
<td>
print.margins
</td>
<td>
Specify the default margins on the printer on Windows in left right top bottom order.
Units depends on your locale, either hundredths of millimetres or thousandths
of inches. You can see which units by the units used in the page setup dialog.
This property is only read at start up.
</td>
</tr>
<tr id='property-print.header.format'>
<td>
<a name='property-print.footer.format'></a>
print.header.format<br />
print.footer.format
</td>
<td>
These settings determine what will be printed if anything as headers and
footers. Property settings can be substituted into the values using the $(property)
syntax. There are some extra properties set up while printing:
CurrentPage, FileTime, FileDate, CurrentDate, and CurrentTime (at start of
printing).
Common properties to use in headers and footers are FileNameExt and FilePath.<br />
A header setting may look like:<br />
<div class="example">
print.header.format=$(FileNameExt) - Printed on $(CurrentDate),$(CurrentTime) - Page $(CurrentPage)
</div>
</td>
</tr>
<tr id='property-print.header.style'>
<td>
<a name='property-print.footer.style'></a>
print.header.style<br />
print.footer.style
</td>
<td>
These settings determine the style of the header and footer using the same
format as other styles in SciTE. Only the fore, back, font, size, bold, italics,
and underlined attributes are supported.
</td>
</tr>
<tr id='property-export.keep.ext'>
<td>
export.keep.ext
</td>
<td>
This property determines how the file name
(for example, LineMarker.cxx) is transformed when
exporting to include the appropriate export format extension -
.html for HTML and .rtf for RTF.
If export.keep.ext is the default, 0, then the current extension is replaced
(LineMarker.html).
If it is 1, then the export format extension is added (LineMarker.cxx.html).
If it is 2 then the final '.' is replaced by '_' and the
export format extension added (LineMarker_cxx.html).
</td>
</tr>
<tr id='property-export.html.wysiwyg'>
<td>
<a name='property-export.html.tabs'></a><a name='property-export.html.folding'></a><a name='property-export.html.styleused'></a><a name='property-export.html.title.fullpath'></a>
export.html.wysiwyg<br />
export.html.tabs<br />
export.html.folding<br />
export.html.styleused<br />
export.html.title.fullpath
</td>
<td>
When export.html.wysiwyg is set to 0 then exporting to a HTML file produces a smaller
file but which is less completely specified so may look more different to the on screen display.
When export.html.tabs is set to 1 and export.html.wysiwyg is set to 0 then tab characters in
the file are exported as tab characters rather than a sequence of space characters.<br />
The exported file can be made to fold in browsers that support CSS well (Mozilla and Internet
Explorer) by setting export.html.folding to 1.
Only export styles actually used when export.html.styleused set to 1.
The full path name of the file is put in the title, instead of just the file name
when export.html.title.fullpath set to 1.
</td>
</tr>
<tr id='property-export.rtf.wysiwyg'>
<td>
<a name='property-export.rtf.tabs'></a><a name='property-export.rtf.font.face'></a><a name='property-export.rtf.font.size'></a><a name='property-export.rtf.tabsize'></a>
export.rtf.wysiwyg<br />
export.rtf.tabs<br />
export.rtf.font.face<br />
export.rtf.font.size<br />
export.rtf.tabsize
</td>
<td>
When export.rtf.wysiwyg is set to 0 then exporting to a RTF file produces a smaller
file but which is less completely specified so may look more different to the on screen display.
When export.rtf.tabs is set to 1 and export.rtf.wysiwyg is set to 0 then tab characters in
the file are exported as tab characters rather than a sequence of space characters. <br />
export.rtf.font.face and export.rtf.font.size can be used to select a particular font and size
for the exported RTF file. export.rtf.tabsize can be set to use a different tab size than that
defined by the tabsize setting.
</td>
</tr>
<tr id='property-export.pdf.magnification'>
<td>
<a name='property-export.pdf.font'></a><a name='property-export.pdf.pagesize'></a><a name='property-export.pdf.margins'></a>
export.pdf.magnification<br />
export.pdf.font<br />
export.pdf.pagesize<br />
export.pdf.margins
</td>
<td>
export.pdf.magnification is a value that is added to the font size of the default screen style in use.
A positive value increases the PDF document's font size, and vice versa.<br />
export.pdf.font accepts a one-word parameter that selects one of the default PDF fonts: Courier,
Helvetica or Times. Helvetica is the default. Helvetica and Times do not line wrap, Courier line
wraps.<br />
export.pdf.pagesize is used to set the document's page size, using points (1/72th of an inch) as
the unit. E.g. Letter paper (8.5 inch x 11 inch) is specified using the values 612,792.<br />
export.pdf.margins sets the widths of the page margins. Margins defaults to 72 points,
or 1 inch.<br />
The PDF exporter is necessarily feature-limited because PDF is a document archival format. Supporting
a full set of features will bloat SciTE. Wrapping Helvetica or Times adequately isn't possible without
the complexities of font metrics and kerning. The PDF produced uses WinAnsiEncoding, so pre-encoding
has to be done before exporting to PDF, if you want to use extended characters.
</td>
</tr>
<tr id='property-export.tex.title.fullpath'>
<td>
export.tex.title.fullpath
</td>
<td>
The full path name of the file is put in the title, instead of just the file name
when export.tex.title.fullpath set to 1.
</td>
</tr>
<tr id='property-export.xml.collapse.spaces'>
<td>
<a name='property-export.xml.collapse.lines'></a>
export.xml.collapse.spaces<br />
export.xml.collapse.lines
</td>
<td>
export.xml.collapse.spaces and export.xml.collapse.lines are flags that control how empty lines
and runs of space characters are converted into XML. The flags are enabled if set to 1. Tab
characters are always converted by the XML exporter into spaces according to the tabsize property.
</td>
</tr>
<tr id='property-fold'>
<td>fold</td>
<td>Folding is turned on by setting fold=1.</td>
</tr>
<tr id='property-fold.symbols'>
<td>
fold.symbols
</td>
<td>
The fold.symbols setting chooses between four ways of showing folding.
Set to 0 (the default) for MacOS style arrows to indicate contracted
(facing right) and expanded (facing down); 1 to display contracted folds
with "+" and expanded with "-"; 2 for a flattened tree control with round
headers and rounded joins; 3 for a flattened tree control with square headers.
</td>
</tr>
<tr id='property-fold.margin.width'>
<td>
fold.margin.width
</td>
<td>
Sets the width of the fold margin.
</td>
</tr>
<tr id='property-fold.margin.colour'>
<td>
<a name='property-fold.margin.highlight.colour'></a>
fold.margin.colour<br />
fold.margin.highlight.colour
</td>
<td>
These two properties defined the fold margin colour and fold
margin highlight colour. If they are not defined (left commented out) the colours for the
fold margin will default to a reasonable pair of colours.
On Windows, the system colours are used to make the fold margin appear like the background
of scroll bars. As an example, with <span class="example">fold.margin.colour=#FF0000</span> and
<span class="example">fold.margin.highlight.colour=#0000FF</span>, the fold margin is a mixture of red
and blue.
</td>
</tr>
<tr id='property-fold.on.open'>
<td>
fold.on.open
</td>
<td>
To automatically fold files as much as possible when loaded, set
fold.on.open to 1.
</td>
</tr>
<tr id='property-fold.flags'>
<td>
fold.flags
</td>
<td>
Not really documented ;) bit flags which may go away.
2, 4, 8, and 16 control drawing lines above and below folding lines if
expanded or not expanded.
Set to 64 to help debug folding by showing hexadecimal fold levels in margin.
</td>
</tr>
<tr id='property-fold.compact'>
<td>
fold.compact<br />
</td>
<td>
For HTML, XML, Lua and C++ and similar files, turning this option on leads to blank lines following the
end of an element folding with that element. Defaults to on.
</td>
</tr>
<tr id='property-fold.highlight'>
<td>
fold.highlight<br />
</td>
<td>
Set to 1 to enable highlight for current folding block (smallest one that contains the caret).
By default, it's disable. Note : The highlight is enabled only when fold.symbols equals
to 2 (round headers) or 3 (square headers).
</td>
</tr>
<tr id='property-fold.highlight.colour'>
<td>
fold.highlight.colour<br />
</td>
<td>
Define the colour of highlight. The colour by default is red (#FF0000).
</td>
</tr>
<tr id='property-title.full.path'>
<td>
title.full.path
</td>
<td>
Chooses how the file name is displayed in the title bar.
When 0 (default) the file name is displayed. When 1 the full path is displayed.
When 2 the window title displays "filename in directory".
</td>
</tr>
<tr id='property-title.show.buffers'>
<td>
title.show.buffers
</td>
<td>
When set to 1 shows the current buffer number in the title bar.
</td>
</tr>
<tr id='property-tabsize'>
<td>
<a name='property-tab.size'></a><a name='property-indent.size'></a><a name='property-use.tabs'></a><a name='property-indent.auto'></a><a name='property-tab.indents'></a><a name='property-backspace.unindents'></a>
tabsize<br />
tab.size.<i>filepattern</i><br />
indent.size<br />
indent.size.<i>filepattern</i><br />
use.tabs<br />
use.tabs.<i>filepattern</i><br />
indent.auto<br />
tab.indents<br />
backspace.unindents
</td>
<td>
Sets the size of a tab as a multiple of the size of a space character in the style of the
default style definition. The indent size is the size to use when performing automatic
indentation and may be different from the tab size. Many people use a tab size of 8 but
4 character indentation. When creating indentation, use.tabs determines whether the
indentation is made up purely from space characters or from a mix of tabs and spaces
using as many tabs as possible. <br />
The global tabsize, indent.size, and use.tabs properties can be overridden for
files that match a pattern by using the file pattern forms: <br />
<div class="example">
indent.size.*.pas=3</div>
If indent.auto is set then indent.size and use.tabs are set according to the contents
of the opened document.<br />
The properties file settings apply to newly opened files but remain constant once the file is open
unless changed using the Change Indentation Settings dialog.<br />
If tab.indents is set then pressing tab within indentation whitespace indents by indent.size
rather than inserting a tab character. If backspace.unindents then pressing backspace
within indentation whitespace unindents by indent.size rather than deleting the character
before the caret.
</td>
</tr>
<tr id='property-indent.automatic'>
<td>
<a name='property-indent.opening'></a><a name='property-indent.closing'></a><a name='property-indent.maintain'></a>
indent.automatic<br />
indent.opening<br />
indent.closing<br />
indent.maintain.<i>filepattern</i>
</td>
<td>
Determines the look of automatic indentation. Automatic indentation is turned on with
indent.automatic=1. To indent a brace line after a compound statement start set
indent.opening=1, likewise for the terminating brace. So with both set to 0:
<div class="example">
if (c)<br />
{<br />
&nbsp;&nbsp;&nbsp;&nbsp;s;<br />
}<br />
</div>
And with both set to 1:
<div class="example">
if (c)<br />
&nbsp;&nbsp;&nbsp;&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;s;<br />
&nbsp;&nbsp;&nbsp;&nbsp;}<br />
</div>
Automatic indentation may be changed to simply repeat the indentation of the
previous line for some files with indent.maintain.<i>filepattern</i>=1 which
overrides the other language specific settings.
</td>
</tr>
<tr id='property-statement.indent'>
<td>
<a name='property-statement.end'></a><a name='property-statement.lookback'></a><a name='property-block.start'></a><a name='property-block.end'></a>
statement.indent.<i>filepattern</i><br />
statement.end.<i>filepattern</i><br />
statement.lookback.<i>filepattern</i><br />
block.start.<i>filepattern</i><br />
block.end.<i>filepattern</i>
</td>
<td>
Each of these settings starts with a style number and then a set of words or characters
that define how to recognise that feature. If there is a second space in the setting then
it is a set of words, otherwise a set of characters. The set of keywords used to indicate
the start of a compound statement is defined in statement.indent. For example:
<div class="example">
statement.indent.$(file.patterns.cpp)=5 if else while
</div>
says that for C++ the words "if", "else", and "while" in keyword style, 5, start compound
statements which leads to the next line being indented if no other factors affect it. However,
if a statement end is found on the same line then the next line is not indented. For C++ the
statement end is the semicolon in the operator style, so this is defined:
<div class="example">
statement.end.$(file.patterns.cpp)=10 ;
</div>
The number of lines looked at to determine indentation can be set with statement.lookback.
This can be used either to bound the amount of time spent on this task or to specify
that only the last line be examined for indentation.<br />
The block.start and block.end properties define the language elements used to bracket groups
of statements. In C++ these are '{' and '}'.
</td>
</tr>
<tr id='property-indent.python.colon'>
<td>
indent.python.colon
</td>
<td>
For Python, automatically indent by one level if the previous line ended in a ':'
ignoring comments and whitespace. Otherwise use the same indentation as the previous line.
This property overrides other indentation settings.
</td>
</tr>
<tr id='property-os.x.home.end.keys'>
<td>
os.x.home.end.keys
</td>
<td>
Chooses the standard OS X behaviour for the Home and End keys which is
to scroll the file to the start or end. This setting takes precedence over
vc.home.key.
</td>
</tr>
<tr id='property-vc.home.key'>
<td>
vc.home.key
</td>
<td>
Chooses the behaviour of the Home and Shift+Home keys. 1, the default is like
Visual C++ moving the caret to the end of the line indentation unless already
there, in which case it moves to the start of the line. 0 moves to the start of the line.
</td>
</tr>
<tr class="windowsonly" id='property-warning.findwrapped'>
<td>
<a name='property-warning.notfound'></a><a name='property-warning.wrongfile'></a><a name='property-warning.executeok'></a><a name='property-warning.executeko'></a><a name='property-warning.nootherbookmark'></a>
warning.findwrapped<br />
warning.notfound<br />
warning.wrongfile<br />
warning.executeok<br />
warning.executeko<br />
warning.nootherbookmark
</td>
<td>
Allows for sounds to be played and the window to be flashed
on Windows when particular events occur.
The values consist of three items separated by ',': flash duration, sound
and sound duration. If sound is a number then it is treated as a pitch and
played for the duration in milliseconds.
Otherwise it is treated as a path to a sound file
that is played. If you do not want a flash, specify 0 for flash duration.
For example,
<div class="example">
warning.wrongfile=0,C:\Windows\Media\SFX\Glass.wav
</div>
will play the glass sound if open selected is given a bad file name.
The findwrapped warning occurs when a find operation wraps past
either end of the file,
notfound when the find or preprocessor conditional move commands
fail to find a match,
executeok when a command such as build
executes successfully, executeko when a command fails, and
nootherbookmark when there is no bookmark to find.
</td>
</tr>
<tr class="gtkonly" id='property-fileselector.width'>
<td>
<a name='property-fileselector.height'></a>
fileselector.width<br />
fileselector.height
</td>
<td>
For the GTK+ version determines the initial size of the file
selector dialog invoked by the Open and Save commands.
Setting has no effect on Windows.
</td>
</tr>
<tr id='property-fileselector.show.hidden' class="osxonly">
<td>
fileselector.show.hidden
</td>
<td>
On OS X setting this to 0 makes the file selector dialog
invoked by the Open command not show hidden files.
</td>
</tr>
<tr id='property-locale.properties'>
<td>
locale.properties
</td>
<td>
Set the name of the localisation file. For a multi-user installation
this allows each user to set a preferred user interface language.<br />
On OS X, localisation files for some languages are installed in the translations
subdirectory of the user home directory which allows setting
the user interface to, for example, German with
<div class="example">
locale.properties=$(SciteUserHome)/translations/locale.de.properties
</div>
</td>
</tr>
<tr id='property-translation.missing'>
<td>
translation.missing
</td>
<td>
When using a localised version, if a term is not found in the locale.properties
translation file then use the value of translation.missing instead. By setting
this to a marker such as "***" it is easier to check where terms have not been
provided with translations.
</td>
</tr>
<tr id='property-menu.language'>
<td>
menu.language
</td>
<td>
Defines the entries in the Language menu and the file extensions they map to.
Each menu item is defined by 3 elements, language name, extension and an optional
keyboard equivalent. Each element is terminated by '|'. For example:<br />
H&amp;ypertext|html|F12|<br />
Menu items may be commented out by prefixing the name with '#'.
</td>
</tr>
<tr class="gtkonly" id='property-menukey.*'>
<td>
menukey.*
</td>
<td>
The menukey.* settings allow the user to redefine accelerator keys for menus
without having to resort to modifying the SciTE source code. The syntax for the setting is:
<div class="example">
menukey.menu_title.menu_name=&lt;modifier&gt;key
</div>
For example, the File | Exit command accelerator could be specified as follows:
<div class="example">
menukey.file.exit=&lt;control&gt;Q
</div>
Note that spaces in menu titles and names must be converted to underscores,
and trailing ellipses removed. For example, "File | Save As...." is referenced as "menukey.file.save_as".
<br /><br />
Multiple modifiers may be specified, though each must be surrounded by angle brackets. The
recognised modifiers are the same as for the user.shortcuts setting described above. The recognised named
keys are also the same as for user.shortcuts, with the addition of "none" to indicate that no accelerator
key should be defined for a particular menu.
</td>
</tr>
<tr class="windowsonly" id='property-source.default.extensions'>
<td>
source.default.extensions
</td>
<td>
If the name specified on the command line cannot be found as a directory or file - including a wild-card
search, the contents of the property are treated as default extensions to be used to locate the file name.<br />
An example is: .cxx|.cpp|.c|.hxx|.hpp|.h|.bat|.txt|.lua<br />
Attempting to open win32\SciTEWin would open win32\SciTEWin.cxx since it matches before win32\SciTEWin.h
<br />
If the property contains an entry such as Bar.cxx|.cxx and you attempt to open win32\SciTEWin, it will open
ScTEWinBar.cxx since that is the first match.
</td>
</tr>
<tr id='property-ext.lua.startup.script'>
<td>
<a name='property-ext.lua.auto.reload'></a><a name='property-ext.lua.reset'></a><a name='property-extension'></a>
ext.lua.startup.script<br />
ext.lua.auto.reload<br />
ext.lua.reset<br />
extension.<i>filepattern</i>
</td>
<td>
The ext.lua properties are specific to the <a href="SciTELua.html">
SciTE Lua Scripting Extension</a>. The extension.<i>filepattern</i> property
is part of the generic <a href="SciTEExtension.html">SciTE Extension
Interface</a> but is currently only used by the Lua Scripting Extension.
<br />
The ext.lua.startup.script property defines the filename of a Lua script that
will be loaded when SciTE starts to set up the global state for Lua.
The default value is $(SciteUserHome)/SciTEStartup.lua.
You should use an absolute path for this property, but can reference the
$(SciteDefaultHome) or $(SciteUserHome) properties. Global event handlers,
command functions, as well as other functions and objects can be defined here.
<br />
The ext.lua.auto.reload property determines what happens if you save the
startup script, or the active extension script, from within SciTE. If it
is set to 0, the startup script only applied at startup time
or when you switch buffers (depending on ext.lua.reset), and changes to the
extension script are only applied when you switch buffers. If
ext.lua.auto.reload is set to 1 (the default), SciTE will re-initialize the global scope
immediately when either script is saved from within SciTE. <i>Even
when ext.lua.auto.reload is enabled, SciTE will not notice if the files
are changed from outside the current SciTE instance. For that, see
ext.lua.reset below.</i>
<br />
The ext.lua.reset property is primarily for debugging. If ext.lua.reset
is 0 (the default), the startup script property is checked only once -
when SciTE starts. If ext.lua.reset is changed to 1, SciTE will check
the startup script property, and reload the new startup script, each
time you switch buffers. As such, it has a different (larger) set of
side effects than ext.lua.auto.reload. In some situations it will make
sense for both auto.reload and reset to be enabled, but usually
ext.lua.auto.reload alone will suffice.
<br />
Aside from ext.lua.startup.script, the extension.<i>filepattern</i> property
provides a way to load additional functions and event handlers that may be
specific to a given file type. If the extension property value ends in .lua
and names a file that exists, the Lua extension evaluates the script so that event
handlers and commands defined in the script are available while that buffer
is active. Functions and objects defined through ext.lua.startup.script are
still accessible, unless they are overridden.
<br />
The extension property can also define behaviour that is specific to a given
directory. If a bare filename (no path) is specified in the extension
property, SciTE looks for the file in the standard property file locations,
starting with the local directory. This can be very useful in combination
with a local SciTE.properties file.
</td>
</tr>
<tr id='property-caret.sticky'>
<td>
caret.sticky
</td>
<td>
Controls when the last position of the caret on the line is modified.
When set to 1, the position is not modified when you type a character, a tab,
paste the clipboard content or press backspace. The default is 0 which turns
off this feature.
</td>
</tr>
<tr id='property-properties.directory.enable'>
<td>
properties.directory.enable
</td>
<td>
Enables or disables the evaluation of the directory properties file.
The default is 0 which disables the evaluation. Any other value enables
this properties file.
</td>
</tr>
</table>
<p>
caret.policy.{x|y}&lt;param&gt; interaction:
</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Caret policy">
<tr>
<th>slop</th>
<th>strict</th>
<th>jumps</th>
<th>even</th>
<th>Caret can go to the margin</th>
<th>When reaching limit<br />
(going out of visibility or<br />
going into the UZ)<br />
display is...</th>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret on top/on right</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved by one position</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret on top/on right</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">1</td>
<td>Yes</td>
<td>centred on the caret</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">0</td>
<td>Caret is always on top/on right of display</td>
<td>-</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">1</td>
<td>No, caret is always centred</td>
<td>-</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret out of the asymmetrical UZ</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved to put caret out of the UZ</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret at 3UZ of the top or right margin</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved to put caret at 3UZ of the margin</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">0</td>
<td>Caret is always at UZ of top/right margin</td>
<td>-</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td>No, kept out of UZ</td>
<td>moved by one position</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">0</td>
<td>No, kept out of UZ</td>
<td>moved to put caret at 3UZ of the margin</td>
</tr>
</table>
<h3 id="IndicatorProperty">
Indicator definition
</h3>
<p>Properties that define indicators look like</p>
<div class="example">
highlight.current.word.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80</div>
<p>The structure uses commas between attributes and a colon between an attribute name and value:</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Caret policy">
<tr>
<th>attribute</th>
<th>value</th>
<th>default</th>
</tr>
<tr>
<td>style</td>
<td>one of plain, squiggle, tt, diagonal, strike, hidden, box, roundbox, straightbox, dash,
dots, squigglelow, dotbox, squigglepixmap, or compositionthick.<br />
</td>
<td>plain</td>
</tr>
<tr>
<td>colour or color</td>
<td>a hex colour value preceded by '#' such as #008020.</td>
<td>black</td>
</tr>
<tr>
<td>fillalpha</td>
<td>the translucency from 0 for completely transparent to 255 for opaque of the fill for roundbox, straightbox and dotbox.</td>
<td>30</td>
</tr>
<tr>
<td>outlinealpha</td>
<td>the translucency from 0 for completely transparent to 255 for opaque of the outline for roundbox, straightbox and dotbox.</td>
<td>50</td>
</tr>
<tr>
<td>under</td>
<td>the indicator is drawn under the text.</td>
<td>no</td>
</tr>
<tr>
<td>notunder</td>
<td>the indicator is drawn over the text.</td>
<td>yes</td>
</tr>
</table>
</p>
<p>Samples:<br />
<img src="SciTEIndicators.png" alt="Indicator samples" /></p>
<h3 id="NewLanguage">
Supporting a new language
</h3>
<p>
For languages very similar to existing supported languages, which may only differ in a minor
feature such as the keywords used, the existing lexers can often be reused. The set of
keywords can then be changed to suit the new language. Java and JavaScript could have
reasonably reused the C++ lexer. The Java lexer was added only to support doc comments.
</p>
<p>
For languages that can not be lexed with the existing lexers, a new lexer can be coded in
C++.&nbsp; These can either be built into Scintilla, or put into an
external module and loaded when SciTE runs (See lexerpath).</p>
<a href="SciTELexer.html">Installing a lexer into SciTE</a>
<br />
<a href="SciTEExternalLexer.html">Creating and installing an external
lexer</a><br />
<p>
The open.filter should be modified to include the file extensions used for the new language
and entries added for command.compile, command.build, command.go and command.go.needs for the
language.
</p>
<h3 id="APIFiles">
Creating API files
</h3>
<p>
The .api files can be generated by hand or by using a program.
There are also <a href="http://code.google.com/p/scite-files/wiki/Customization">downloadable ready-to-use
.api files.</a>
</p>
<p>
For C/C++ headers, an API file can be generated using
<a href="http://ctags.sourceforge.net/">ctags</a>
and then the <a href="tags2api.py">
tags2api Python script</a> (which assumes C/C++ source) on the tags file to grab complete
multiple line function prototypes.
Some common headers surround parameter lists with a __P macro and may have
comments. The <a href="cleanapi.cc">cleanapi</a> utility may be used on these files.
</p>
<p>
To generate an API file for Python modules, there is a
<a href="gen_python_api.zip">gen_python script</a>.
</p>
<p>
To generate an API file for Java classes, there is a
<a href="ApiBuilder.java">ApiBuilder.java</a> program.
</p>
<h3 id="OpenSelected">
Open Selected Filename
</h3>
<p>
This command opens the file for the file name selected in either the edit or output pane.
It uses the current selection or searches around the caret to try to
find a file name based on which characters are normally used in a path.
If there is no extension then an extension may be inferred from the current file using the
open.suffix property which defaults to .properties in a .properties file.
If the file name is followed by a number (in a format similar to ctags, grep output,
or Visual Studio messages) then that line is displayed in the opened file.
If the file name is an absolute path then it is opened directly otherwise it is looked for
in the current directory and then in the directory specified by the openpath property.
On Windows, web, ftp, mail and news URLs are handled by opening their
associated application.
</p>
<h3 id="Translations">
SciTE in other languages
</h3>
<p>
SciTE can be and has been <a href="http://code.google.com/p/scite-files/wiki/Translations">translated into other languages</a>.
</p>
<h3 id="Building">
Building SciTE
</h3>
<p>
The procedure for building and installing SciTE is described in the README file in the scite
directory.
</p>
<h3 id="Extending">
Extending SciTE
</h3>
<p>
There are two formal extension interfaces for SciTE, the
<a href="SciTEExtension.html">SciTE Extension Interface</a>
is for extending SciTE with code compiled into the SciTE executable and the
<a href="SciTEDirector.html">SciTE Director Interface</a> is for
manipulating SciTE on Windows from another application.
</p>
</body>
</html>