/usr/share/doc/zsh-common/html/User-Contributions.html is in zsh-doc 5.1.1-1ubuntu2.3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>zsh: 26 User Contributions</title>
<meta name="description" content="zsh: 26 User Contributions">
<meta name="keywords" content="zsh: 26 User Contributions">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2any">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="User-Contributions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="Zftp-Function-System.html#Zftp-Function-System" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="Zftp-Function-System.html#Completion-4" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Description-9" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="User-Contributions-1"></a>
<h1 class="chapter">26 User Contributions</h1>
<p><a name="index-user-contributions"></a>
</p>
<hr>
<a name="Description-9"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h2 class="section">26.1 Description</h2>
<p>The Zsh source distribution includes a number of items contributed by the
user community. These are not inherently a part of the shell, and some
may not be available in every zsh installation. The most significant of
these are documented here. For documentation on other contributed items
such as shell functions, look for comments in the function source files.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#Utilities">26.2 Utilities</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Recent-Directories">26.3 Remembering Recent Directories</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Version-Control-Information">26.4 Gathering information from version control systems</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Prompt-Themes">26.5 Prompt Themes</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#ZLE-Functions">26.6 ZLE Functions</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Exception-Handling">26.7 Exception Handling</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#MIME-Functions">26.8 MIME Functions</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Mathematical-Functions">26.9 Mathematical Functions</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#User-Configuration-Functions">26.10 User Configuration Functions</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#Other-Functions">26.11 Other Functions</a></td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<hr>
<a name="Utilities"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Description-9" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Accessing-On_002dLine-Help" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Utilities-1"></a>
<h2 class="section">26.2 Utilities</h2>
<hr>
<a name="Accessing-On_002dLine-Help"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Recompiling-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.2.1 Accessing On-Line Help</h3>
<p><a name="index-helpfiles-utility"></a>
</p>
<p>The key sequence <tt>ESC h</tt> is normally bound by ZLE to execute the
<tt>run-help</tt> widget (see
<a href="Zsh-Line-Editor.html#Zsh-Line-Editor">Zsh Line Editor</a>). This invokes the <tt>run-help</tt> command with the command word from the
current input line as its argument. By default, <tt>run-help</tt> is an alias
for the <tt>man</tt> command, so this often fails when the command word is a
shell builtin or a user-defined function. By redefining the <tt>run-help</tt>
alias, one can improve the on-line help provided by the shell.
</p>
<p>The <tt>helpfiles</tt> utility, found in the <tt>Util</tt> directory of the
distribution, is a Perl program that can be used to process the zsh manual
to produce a separate help file for each shell builtin and for many other
shell features as well. The autoloadable <tt>run-help</tt> function, found in
<tt>Functions/Misc</tt>, searches for these helpfiles and performs several
other tests to produce the most complete help possible for the command.
</p>
<p>Help files are installed by default to a subdirectory of <tt>/usr/share/zsh</tt>
or <tt>/usr/local/share/zsh</tt>.
</p>
<p>To create your own help files with <tt>helpfiles</tt>, choose or create a
directory where the individual command help files will reside. For
example, you might choose <tt>~/zsh_help</tt>. If you unpacked the zsh
distribution in your home directory, you would use the commands:
</p>
<div class="example">
<pre class="example">mkdir ~/zsh_help
perl ~/zsh-5.1.1/Util/helpfiles ~/zsh_help
</pre></div>
<p><a name="index-HELPDIR"></a>
The <tt>HELPDIR</tt> parameter tells <tt>run-help</tt> where to look for the help
files. When unset, it uses the default installation path.
To use your own set of help files, set this to the appropriate path
in one of your startup files:
</p>
<div class="example">
<pre class="example">HELPDIR=~/zsh_help
</pre></div>
<p><a name="index-run_002dhelp_002c-use-of"></a>
To use the <tt>run-help</tt> function, you need to add lines something
like the following to your <tt>.zshrc</tt> or equivalent startup file:
</p>
<div class="example">
<pre class="example">unalias run-help
autoload run-help
</pre></div>
<p>Note that in order for ‘<tt>autoload run-help</tt>’ to work, the <tt>run-help</tt>
file must be in one of the directories named in your <tt>fpath</tt> array (see
<a href="Parameters.html#Parameters-Used-By-The-Shell">Parameters Used By The Shell</a>). This should already be the case if you have a standard zsh
installation; if it is not, copy <tt>Functions/Misc/run-help</tt> to an
appropriate directory.
</p>
<hr>
<a name="Recompiling-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Accessing-On_002dLine-Help" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Keyboard-Definition" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.2.2 Recompiling Functions</h3>
<p><a name="index-functions_002c-recompiling"></a>
<a name="index-zrecompile-utility"></a>
</p>
<p>If you frequently edit your zsh functions, or periodically update your zsh
installation to track the latest developments, you may find that function
digests compiled with the <tt>zcompile</tt> builtin are frequently out of date
with respect to the function source files. This is not usually a problem,
because zsh always looks for the newest file when loading a function, but
it may cause slower shell startup and function loading. Also, if a digest
file is explicitly used as an element of <tt>fpath</tt>, zsh won’t check whether
any of its source files has changed.
</p>
<p>The <tt>zrecompile</tt> autoloadable function, found in <tt>Functions/Misc</tt>, can
be used to keep function digests up to date.
</p>
<dl compact="compact">
<dd><a name="index-zrecompile"></a>
</dd>
<dt><tt>zrecompile</tt> [ <tt>-qt</tt> ] [ <var>name</var> ... ]</dt>
<dt><tt>zrecompile</tt> [ <tt>-qt</tt> ] <tt>-p</tt> <var>arg</var> ... [ <tt>-</tt><tt>-</tt> <var>arg</var> ... ]</dt>
<dd><p>This tries to find <tt>*.zwc</tt> files and automatically re-compile them if at
least one of the original files is newer than the compiled file. This
works only if the names stored in the compiled files are full paths or are
relative to the directory that contains the <tt>.zwc</tt> file.
</p>
<p>In the first form, each <var>name</var> is the name of a compiled file or a
directory containing <tt>*.zwc</tt> files that should be checked. If no
arguments are given, the directories and <tt>*.zwc</tt> files in <tt>fpath</tt> are
used.
</p>
<p>When <tt>-t</tt> is given, no compilation is performed, but a return status of
zero (true) is set if there are files that need to be re-compiled and
non-zero (false) otherwise. The <tt>-q</tt> option quiets the chatty output
that describes what <tt>zrecompile</tt> is doing.
</p>
<p>Without the <tt>-t</tt> option, the return status is zero if all files that
needed re-compilation could be compiled and non-zero if compilation for at
least one of the files failed.
</p>
<p>If the <tt>-p</tt> option is given, the <var>arg</var>s are interpreted as one
or more sets of arguments for <tt>zcompile</tt>, separated by ‘<tt>-</tt><tt>-</tt>’.
For example:
</p>
<div class="example">
<pre class="example">zrecompile -p \
-R ~/.zshrc -- \
-M ~/.zcompdump -- \
~/zsh/comp.zwc ~/zsh/Completion/*/_*
</pre></div>
<p>This compiles <tt>~/.zshrc</tt> into <tt>~/.zshrc.zwc</tt> if that doesn’t exist or
if it is older than <tt>~/.zshrc</tt>. The compiled file will be marked for
reading instead of mapping. The same is done for <tt>~/.zcompdump</tt> and
<tt>~/.zcompdump.zwc</tt>, but this compiled file is marked for mapping. The
last line re-creates the file <tt>~/zsh/comp.zwc</tt> if any of the files
matching the given pattern is newer than it.
</p>
<p>Without the <tt>-p</tt> option, <tt>zrecompile</tt> does not create function digests
that do not already exist, nor does it add new functions to the digest.
</p>
</dd>
</dl>
<p>The following shell loop is an example of a method for creating function
digests for all functions in your <tt>fpath</tt>, assuming that you have write
permission to the directories:
</p>
<div class="example">
<pre class="example">for ((i=1; i <= $#fpath; ++i)); do
dir=$fpath[i]
zwc=${dir:t}.zwc
if [[ $dir == (.|..) || $dir == (.|..)/* ]]; then
continue
fi
files=($dir/*(N-.))
if [[ -w $dir:h && -n $files ]]; then
files=(${${(M)files%/*/*}#/})
if ( cd $dir:h &&
zrecompile -p -U -z $zwc $files ); then
fpath[i]=$fpath[i].zwc
fi
fi
done
</pre></div>
<p>The <tt>-U</tt> and <tt>-z</tt> options are appropriate for functions in the default
zsh installation <tt>fpath</tt>; you may need to use different options for your
personal function directories.
</p>
<p>Once the digests have been created and your <tt>fpath</tt> modified to refer to
them, you can keep them up to date by running <tt>zrecompile</tt> with no
arguments.
</p>
<hr>
<a name="Keyboard-Definition"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Recompiling-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Dumping-Shell-State" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.2.3 Keyboard Definition</h3>
<p><a name="index-keyboard-definition"></a>
</p>
<p><a name="index-zkbd"></a>
The large number of possible combinations of keyboards, workstations,
terminals, emulators, and window systems makes it impossible for zsh to
have built-in key bindings for every situation. The <tt>zkbd</tt> utility,
found in <tt>Functions/Misc</tt>, can help you quickly create key bindings for your
configuration.
</p>
<p>Run <tt>zkbd</tt> either as an autoloaded function, or as a shell script:
</p>
<div class="example">
<pre class="example">zsh -f ~/zsh-5.1.1/Functions/Misc/zkbd
</pre></div>
<p>When you run <tt>zkbd</tt>, it first asks you to enter your terminal type; if
the default it offers is correct, just press return. It then asks you to
press a number of different keys to determine characteristics of your
keyboard and terminal; <tt>zkbd</tt> warns you if it finds anything out of the
ordinary, such as a Delete key that sends neither <tt>^H</tt> nor <tt>^?</tt>.
</p>
<p>The keystrokes read by <tt>zkbd</tt> are recorded as a definition for an
associative array named <tt>key</tt>, written to a file in the subdirectory
<tt>.zkbd</tt> within either your <tt>HOME</tt> or <tt>ZDOTDIR</tt> directory. The name
of the file is composed from the <tt>TERM</tt>, <tt>VENDOR</tt> and <tt>OSTYPE</tt>
parameters, joined by hyphens.
</p>
<p>You may read this file into your <tt>.zshrc</tt> or another startup file with
the ‘<tt>source</tt>’ or ‘<tt>.</tt>’ commands, then reference the <tt>key</tt> parameter
in bindkey commands, like this:
</p>
<div class="example">
<pre class="example">source ${ZDOTDIR:-$HOME}/.zkbd/$TERM-$VENDOR-$OSTYPE
[[ -n ${key[Left]} ]] && bindkey "${key[Left]}" backward-char
[[ -n ${key[Right]} ]] && bindkey "${key[Right]}" forward-char
# etc.
</pre></div>
<p>Note that in order for ‘<tt>autoload zkbd</tt>’ to work, the <tt>zkdb</tt> file must
be in one of the directories named in your <tt>fpath</tt> array (see
<a href="Parameters.html#Parameters-Used-By-The-Shell">Parameters Used By The Shell</a>). This should already be the case if you have a standard zsh
installation; if it is not, copy <tt>Functions/Misc/zkbd</tt> to an
appropriate directory.
</p>
<hr>
<a name="Dumping-Shell-State"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Keyboard-Definition" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Manipulating-Hook-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.2.4 Dumping Shell State</h3>
<p><a name="index-reporter-utility"></a>
</p>
<p>Occasionally you may encounter what appears to be a bug in the shell,
particularly if you are using a beta version of zsh or a development
release. Usually it is sufficient to send a description of the
problem to one of the zsh mailing lists (see
<a href="Introduction.html#Mailing-Lists">Mailing Lists</a>), but sometimes one of the zsh developers will need to recreate your
environment in order to track the problem down.
</p>
<p>The script named <tt>reporter</tt>, found in the <tt>Util</tt> directory of the
distribution, is provided for this purpose. (It is also possible to
<tt>autoload reporter</tt>, but <tt>reporter</tt> is not installed in <tt>fpath</tt>
by default.) This script outputs a detailed dump of the shell state,
in the form of another script that can be read with ‘<tt>zsh -f</tt>’ to
recreate that state.
</p>
<p>To use <tt>reporter</tt>, read the script into your shell with the ‘<tt>.</tt>’
command and redirect the output into a file:
</p>
<div class="example">
<pre class="example">. ~/zsh-5.1.1/Util/reporter > zsh.report
</pre></div>
<p>You should check the <tt>zsh.report</tt> file for any sensitive information
such as passwords and delete them by hand before sending the script to the
developers. Also, as the output can be voluminous, it’s best to wait for
the developers to ask for this information before sending it.
</p>
<p>You can also use <tt>reporter</tt> to dump only a subset of the shell state.
This is sometimes useful for creating startup files for the first time.
Most of the output from reporter is far more detailed than usually is
necessary for a startup file, but the <tt>aliases</tt>, <tt>options</tt>, and
<tt>zstyles</tt> states may be useful because they include only changes from
the defaults. The <tt>bindings</tt> state may be useful if you have created
any of your own keymaps, because <tt>reporter</tt> arranges to dump the keymap
creation commands as well as the bindings for every keymap.
</p>
<p>As is usual with automated tools, if you create a startup file with
<tt>reporter</tt>, you should edit the results to remove unnecessary commands.
Note that if you’re using the new completion system, you should <em>not</em>
dump the <tt>functions</tt> state to your startup files with <tt>reporter</tt>; use
the <tt>compdump</tt> function instead (see
<a href="Completion-System.html#Completion-System">Completion System</a>).
</p>
<dl compact="compact">
<dt><tt>reporter</tt> [ <var>state</var> ... ]</dt>
<dd><a name="index-reporter"></a>
<p>Print to standard output the indicated subset of the current shell state.
The <var>state</var> arguments may be one or more of:
</p>
<dl compact="compact">
<dt><tt>all</tt></dt>
<dd><p>Output everything listed below.
</p></dd>
<dt><tt>aliases</tt></dt>
<dd><p>Output alias definitions.
</p></dd>
<dt><tt>bindings</tt></dt>
<dd><p>Output ZLE key maps and bindings.
</p></dd>
<dt><tt>completion</tt></dt>
<dd><p>Output old-style <tt>compctl</tt> commands.
New completion is covered by <tt>functions</tt> and <tt>zstyles</tt>.
</p></dd>
<dt><tt>functions</tt></dt>
<dd><p>Output autoloads and function definitions.
</p></dd>
<dt><tt>limits</tt></dt>
<dd><p>Output <tt>limit</tt> commands.
</p></dd>
<dt><tt>options</tt></dt>
<dd><p>Output <tt>setopt</tt> commands.
</p></dd>
<dt><tt>styles</tt></dt>
<dd><p>Same as <tt>zstyles</tt>.
</p></dd>
<dt><tt>variables</tt></dt>
<dd><p>Output shell parameter assignments, plus <tt>export</tt>
commands for any environment variables.
</p></dd>
<dt><tt>zstyles</tt></dt>
<dd><p>Output <tt>zstyle</tt> commands.
</p></dd>
</dl>
<p>If the <var>state</var> is omitted, <tt>all</tt> is assumed.
</p>
<p>With the exception of ‘<tt>all</tt>’, every <var>state</var> can be abbreviated by
any prefix, even a single letter; thus <tt>a</tt> is the same as <tt>aliases</tt>,
<tt>z</tt> is the same as <tt>zstyles</tt>, etc.
</p></dd>
</dl>
<hr>
<a name="Manipulating-Hook-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Dumping-Shell-State" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Utilities" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.2.5 Manipulating Hook Functions</h3>
<p><a name="index-hook-function-utility"></a>
</p>
<dl compact="compact">
<dd><a name="index-add_002dzsh_002dhook"></a>
</dd>
<dt><tt>add-zsh-hook</tt> [ <tt>-dD</tt> ] [ <tt>-Uzk</tt> ] <var>hook</var> <var>function</var></dt>
<dd><p>Several functions are special to the shell, as described in the section
Special Functions, <a href="Functions.html#Functions">Functions</a>,
in that they are automatic called at a specific point during shell execution.
Each has an associated array consisting of names of functions to be
called at the same point; these are so-called ‘hook functions’.
The shell function <tt>add-zsh-hook</tt> provides a simple way of adding or
removing functions from the array.
</p>
<p><var>hook</var> is one of <tt>chpwd</tt>, <tt>periodic</tt>, <tt>precmd</tt>, <tt>preexec</tt>,
<tt>zshaddhistory</tt>, <tt>zshexit</tt>, or <tt>zsh_directory_name</tt>,
the special functions in question. Note that <tt>zsh_directory_name</tt>
is called in a different way from the other functions, but may
still be manipulated as a hook.
</p>
<p><var>function</var> is name of an ordinary shell function. If no options
are given this will be added to the array of functions to be executed
in the given context.
</p>
<p>If the option <tt>-d</tt> is given, the <var>function</var> is removed from
the array of functions to be executed.
</p>
<p>If the option <tt>-D</tt> is given, the <var>function</var> is treated as a pattern
and any matching names of functions are removed from the array of
functions to be executed.
</p>
<p>The options <tt>-U</tt>, <tt>-z</tt> and <tt>-k</tt> are passed as arguments to
<tt>autoload</tt> for <var>function</var>. For functions contributed with zsh, the
options <tt>-Uz</tt> are appropriate.
</p>
</dd>
</dl>
<hr>
<a name="Recent-Directories"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Manipulating-Hook-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Installation-2" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="index-recent-directories_002c-maintaining-list-of"></a>
<a name="index-directories_002c-maintaining-list-of-recent"></a>
<a name="index-cdr"></a>
<a name="index-_005fcdr"></a>
<a name="index-chpwd_005frecent_005fadd"></a>
<a name="index-chpwd_005frecent_005fdirs"></a>
<a name="index-chpwd_005frecent_005ffilehandler"></a>
<a name="Remembering-Recent-Directories"></a>
<h2 class="section">26.3 Remembering Recent Directories</h2>
<p>The function <tt>cdr</tt> allows you to change the working directory to a
previous working directory from a list maintained automatically. It is
similar in concept to the directory stack controlled by the <tt>pushd</tt>,
<tt>popd</tt> and <tt>dirs</tt> builtins, but is more configurable, and as it stores
all entries in files it is maintained across sessions and (by default)
between terminal emulators in the current session. Duplicates are
automatically removed, so that the list reflects the single most recent
use of each directory.
</p>
<p>Note that the <tt>pushd</tt> directory stack is not actually modified or used
by <tt>cdr</tt> unless you configure it to do so as described in the
configuration section below.
</p>
<hr>
<a name="Installation-2"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Use" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.1 Installation</h3>
<p>The system works by means of a hook function that is called every time the
directory changes. To install the system, autoload the required functions
and use the <tt>add-zsh-hook</tt> function described above:
</p>
<div class="example">
<pre class="example">autoload -Uz chpwd_recent_dirs cdr add-zsh-hook
add-zsh-hook chpwd chpwd_recent_dirs
</pre></div>
<p>Now every time you change directly interactively, no matter which
command you use, the directory to which you change will be remembered
in most-recent-first order.
</p>
<hr>
<a name="Use"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation-2" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Options-3" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.2 Use</h3>
<p>All direct user interaction is via the <tt>cdr</tt> function.
</p>
<p>The argument to cdr is a number <var>N</var> corresponding to the <var>N</var>th most
recently changed-to directory. 1 is the immediately preceding directory;
the current directory is remembered but is not offered as a destination.
Note that if you have multiple windows open 1 may refer to a directory
changed to in another window; you can avoid this by having per-terminal
files for storing directory as described for the
<tt>recent-dirs-file</tt> style below.
</p>
<p>If you set the <tt>recent-dirs-default</tt> style described below <tt>cdr</tt>
will behave the same as <tt>cd</tt> if given a non-numeric argument, or more
than one argument. The recent directory list is updated just the same
however you change directory.
</p>
<p>If the argument is omitted, 1 is assumed. This is similar to <tt>pushd</tt>’s
behaviour of swapping the two most recent directories on the stack.
</p>
<p>Completion for the argument to <tt>cdr</tt> is available if compinit has been
run; menu selection is recommended, using:
</p>
<div class="example">
<pre class="example">zstyle ':completion:*:*:cdr:*:*' menu selection
</pre></div>
<p>to allow you to cycle through recent directories; the order is preserved,
so the first choice is the most recent directory before the current one.
The verbose style is also recommended to ensure the directory is shown; this
style is on by default so no action is required unless you have changed it.
</p>
<hr>
<a name="Options-3"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Use" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Configuration-1" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.3 Options</h3>
<p>The behaviour of <tt>cdr</tt> may be modified by the following options.
</p>
<dl compact="compact">
<dt><tt>-l</tt></dt>
<dd><p>lists the numbers and the corresponding directories in
abbreviated form (i.e. with <tt>~</tt> substitution reapplied), one per line.
The directories here are not quoted (this would only be an issue if a
directory name contained a newline). This is used by the completion
system.
</p>
</dd>
<dt><tt>-r</tt></dt>
<dd><p>sets the variable <tt>reply</tt> to the current set of directories. Nothing
is printed and the directory is not changed.
</p>
</dd>
<dt><tt>-e</tt></dt>
<dd><p>allows you to edit the list of directories, one per line. The
list can be edited to any extent you like; no sanity checking is
performed. Completion is available. No quoting is necessary (except for
newlines, where I have in any case no sympathy); directories are in
unabbreviated from and contain an absolute path, i.e. they start with <tt>/</tt>.
Usually the first entry should be left as the current directory.
</p>
</dd>
</dl>
<hr>
<a name="Configuration-1"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Options-3" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Use-with-dynamic-directory-naming" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.4 Configuration</h3>
<p>Configuration is by means of the styles mechanism that should be familiar
from completion; if not, see the description of the <tt>zstyle</tt> command in
<a href="Zsh-Modules.html#The-zsh_002fzutil-Module">The zsh/zutil Module</a>. The context for setting styles
should be <tt>':chpwd:*'</tt> in case the meaning of the context is extended in
future, for example:
</p>
<div class="example">
<pre class="example">zstyle ':chpwd:*' recent-dirs-max 0
</pre></div>
<p>sets the value of the <tt>recent-dirs-max</tt> style to 0. In practice the
style name is specific enough that a context of ’*’ should be fine.
</p>
<p>An exception is <tt>recent-dirs-insert</tt>, which is used exclusively by the
completion system and so has the usual completion system context
(<tt>':completion:*'</tt> if nothing more specific is needed), though again
<tt>'*'</tt> should be fine in practice.
</p>
<dl compact="compact">
<dt><tt>recent-dirs-default</tt></dt>
<dd><p>If true, and the command is expecting a recent directory index, and
either there is more than one argument or the argument is not an
integer, then fall through to "cd". This allows the lazy to use only
one command for directory changing. Completion recognises this, too;
see recent-dirs-insert for how to control completion when this option
is in use.
</p>
</dd>
<dt><tt>recent-dirs-file</tt></dt>
<dd><p>The file where the list of directories is saved. The default
is <tt>${ZDOTDIR:-$HOME}/.chpwd-recent-dirs</tt>, i.e. this is in your
home directory unless you have set the variable <tt>ZDOTDIR</tt> to point
somewhere else. Directory names are saved in <tt>$'</tt><var>...</var><tt>'</tt> quoted
form, so each line in the file can be supplied directly to the shell as an
argument.
</p>
<p>The value of this style may be an array. In this case, the first
file in the list will always be used for saving directories while any
other files are left untouched. When reading the recent directory
list, if there are fewer than the maximum number of entries in the
first file, the contents of later files in the array will be appended
with duplicates removed from the list shown. The contents of the two
files are not sorted together, i.e. all the entries in the first file
are shown first. The special value <tt>+</tt> can appear in the list to
indicate the default file should be read at that point. This allows
effects like the following:
</p>
<div class="example">
<pre class="example">zstyle ':chpwd:*' recent-dirs-file \
~/.chpwd-recent-dirs-${TTY##*/} +
</pre></div>
<p>Recent directories are read from a file numbered according to
the terminal. If there are insufficient entries the list
is supplemented from the default file.
</p>
<p>It is possible to use <tt>zstyle -e</tt> to make the directory configurable
at run time:
</p>
<div class="example">
<pre class="example">zstyle -e ':chpwd:*' recent-dirs-file pick-recent-dirs-file
pick-recent-dirs-file() {
if [[ $PWD = ~/text/writing(|/*) ]]; then
reply=(~/.chpwd-recent-dirs-writing)
else
reply=(+)
fi
}
</pre></div>
<p>In this example, if the current directory is <tt>~/text/writing</tt> or a
directory under it, then use a special file for saving recent
directories, else use the default.
</p>
</dd>
<dt><tt>recent-dirs-insert</tt></dt>
<dd><p>Used by completion. If <tt>recent-dirs-default</tt> is true, then setting
this to <tt>true</tt> causes the actual directory, rather than its index, to
be inserted on the command line; this has the same effect as using
the corresponding index, but makes the history clearer and the line
easier to edit. With this setting, if part of an argument was
already typed, normal directory completion rather than recent
directory completion is done; this is because recent directory
completion is expected to be done by cycling through entries menu
fashion.
</p>
<p>If the value of the style is <tt>always</tt>, then only recent directories will
be completed; in that case, use the <tt>cd</tt> command when you want to
complete other directories.
</p>
<p>If the value is <tt>fallback</tt>, recent directories will be tried first, then
normal directory completion is performed if recent directory completion
failed to find a match.
</p>
<p>Finally, if the value is <tt>both</tt> then both sets of completions are
presented; the usual tag mechanism can be used to distinguish results, with
recent directories tagged as <tt>recent-dirs</tt>. Note that the recent
directories inserted are abbreviated with directory names where appropriate.
</p>
</dd>
<dt><tt>recent-dirs-max</tt></dt>
<dd><p>The maximum number of directories to save to the file. If
this is zero or negative there is no maximum. The default is 20.
Note this includes the current directory, which isn’t offered,
so the highest number of directories you will be offered
is one less than the maximum.
</p>
</dd>
<dt><tt>recent-dirs-prune</tt></dt>
<dd><p>This style is an array determining what directories should (or should
not) be added to the recent list. Elements of the array can include:
</p>
<dl compact="compact">
<dt><tt>parent</tt></dt>
<dd><p>Prune parents (more accurately, ancestors) from the recent list.
If present, changing directly down by any number of directories
causes the current directory to be overwritten. For example,
changing from ~pws to ~pws/some/other/dir causes ~pws not to be
left on the recent directory stack. This only applies to direct
changes to descendant directories; earlier directories on the
list are not pruned. For example, changing from ~pws/yet/another
to ~pws/some/other/dir does not cause ~pws to be pruned.
</p>
</dd>
<dt><tt>pattern:<var>pattern</var></tt></dt>
<dd><p>Gives a zsh pattern for directories that should not be
added to the recent list (if not already there). This element
can be repeated to add different patterns. For example,
<tt>'pattern:/tmp(|/*)'</tt> stops <tt>/tmp</tt> or its descendants
from being added. The <tt>EXTENDED_GLOB</tt> option is always turned on
for these patterns.
</p>
</dd>
</dl>
</dd>
<dt><tt>recent-dirs-pushd</tt></dt>
<dd><p>If set to true, <tt>cdr</tt> will use <tt>pushd</tt> instead of <tt>cd</tt> to change the
directory, so the directory is saved on the directory stack. As the
directory stack is completely separate from the list of files saved
by the mechanism used in this file there is no obvious reason to do
this.
</p>
</dd>
</dl>
<hr>
<a name="Use-with-dynamic-directory-naming"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Configuration-1" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Details-of-directory-handling" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.5 Use with dynamic directory naming</h3>
<p>It is possible to refer to recent directories using the dynamic directory
name syntax by using the supplied function <tt>zsh_directory_name_cdr</tt>
a hook:
</p>
<div class="example">
<pre class="example">autoload -Uz add-zsh-hook
add-zsh-hook -Uz zsh_directory_name zsh_directory_name_cdr
</pre></div>
<p>When this is done, <tt>~[1]</tt> will refer to the most recent
directory other than $PWD, and so on. Completion after <tt>~[</tt><var>...</var>
also works.
</p>
<hr>
<a name="Details-of-directory-handling"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Use-with-dynamic-directory-naming" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Recent-Directories" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.3.6 Details of directory handling</h3>
<p>This section is for the curious or confused; most users will not
need to know this information.
</p>
<p>Recent directories are saved to a file immediately and hence are
preserved across sessions. Note currently no file locking is applied:
the list is updated immediately on interactive commands and nowhere else
(unlike history), and it is assumed you are only going to change
directory in one window at once. This is not safe on shared accounts,
but in any case the system has limited utility when someone else is
changing to a different set of directories behind your back.
</p>
<p>To make this a little safer, only directory changes instituted from the
command line, either directly or indirectly through shell function calls
(but not through subshells, evals, traps, completion functions and the
like) are saved. Shell functions should use <tt>cd -q</tt> or <tt>pushd -q</tt> to
avoid side effects if the change to the directory is to be invisible at the
command line. See the contents of the function <tt>chpwd_recent_dirs</tt> for
more details.
</p>
<hr>
<a name="Version-Control-Information"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Details-of-directory-handling" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Quickstart" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Gathering-information-from-version-control-systems"></a>
<h2 class="section">26.4 Gathering information from version control systems</h2>
<p><a name="index-version-control-utility"></a>
</p>
<p>In a lot of cases, it is nice to automatically retrieve information from
version control systems (VCSs), such as subversion, CVS or git, to be able
to provide it to the user; possibly in the user’s prompt. So that you can
instantly tell which branch you are currently on, for example.
</p>
<p>In order to do that, you may use the <tt>vcs_info</tt> function.
</p>
<p>The following VCSs are supported, showing the abbreviated name by which
they are referred to within the system:
</p><dl compact="compact">
<dt>Bazaar (<tt>bzr</tt>)</dt>
<dd><p><tt><a href="http://bazaar.canonical.com/">http://bazaar.canonical.com/</a></tt>
</p></dd>
<dt>Codeville (<tt>cdv</tt>)</dt>
<dd><p><tt><a href="http://freecode.com/projects/codeville/">http://freecode.com/projects/codeville/</a></tt>
</p></dd>
<dt>Concurrent Versioning System (<tt>cvs</tt>)</dt>
<dd><p><tt><a href="http://www.nongnu.org/cvs/">http://www.nongnu.org/cvs/</a></tt>
</p></dd>
<dt>Darcs (<tt>darcs</tt>)</dt>
<dd><p><tt><a href="http://darcs.net/">http://darcs.net/</a></tt>
</p></dd>
<dt>Fossil (<tt>fossil</tt>)</dt>
<dd><p><tt><a href="http://fossil-scm.org/">http://fossil-scm.org/</a></tt>
</p></dd>
<dt>Git (<tt>git</tt>)</dt>
<dd><p><tt><a href="http://git-scm.com/">http://git-scm.com/</a></tt>
</p></dd>
<dt>GNU arch (<tt>tla</tt>)</dt>
<dd><p><tt><a href="http://www.gnu.org/software/gnu-arch/">http://www.gnu.org/software/gnu-arch/</a></tt>
</p></dd>
<dt>Mercurial (<tt>hg</tt>)</dt>
<dd><p><tt><a href="http://mercurial.selenic.com/">http://mercurial.selenic.com/</a></tt>
</p></dd>
<dt>Monotone (<tt>mtn</tt>)</dt>
<dd><p><tt><a href="http://monotone.ca/">http://monotone.ca/</a></tt>
</p></dd>
<dt>Perforce (<tt>p4</tt>)</dt>
<dd><p><tt><a href="http://www.perforce.com/">http://www.perforce.com/</a></tt>
</p></dd>
<dt>Subversion (<tt>svn</tt>)</dt>
<dd><p><tt><a href="http://subversion.apache.org/">http://subversion.apache.org/</a></tt>
</p></dd>
<dt>SVK (<tt>svk</tt>)</dt>
<dd><p><tt><a href="http://svk.bestpractical.com/">http://svk.bestpractical.com/</a></tt>
</p></dd>
</dl>
<p>There is also support for the patch management system <tt>quilt</tt>
(<tt><a href="http://savannah.nongnu.org/projects/quilt">http://savannah.nongnu.org/projects/quilt</a></tt>). See <tt>Quilt Support</tt>
below for details.
</p>
<p>To load <tt>vcs_info</tt>:
</p>
<div class="example">
<pre class="example">autoload -Uz vcs_info
</pre></div>
<p>It can be used in any existing prompt, because it does not require any
specific <tt>$psvar</tt> entries to be available.
</p>
<hr>
<a name="Quickstart"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Configuration-2" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.1 Quickstart</h3>
<p>To get this feature working quickly (including colors), you can do the
following (assuming, you loaded <tt>vcs_info</tt> properly - see above):
</p>
<div class="example">
<pre class="example">zstyle ':vcs_info:*' actionformats \
'%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{3}|%F{1}%a%F{5}]%f '
zstyle ':vcs_info:*' formats \
'%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{5}]%f '
zstyle ':vcs_info:(sv[nk]|bzr):*' branchformat '%b%F{1}:%F{3}%r'
precmd () { vcs_info }
PS1='%F{5}[%F{2}%n%F{5}] %F{3}%3~ ${vcs_info_msg_0_}%f%# '
</pre></div>
<p>Obviously, the last two lines are there for demonstration. You need to
call <tt>vcs_info</tt> from your <tt>precmd</tt> function. Once that is done you need
a <em>single quoted</em> <tt>'${vcs_info_msg_0_}'</tt> in your prompt.
</p>
<p>To be able to use <tt>'${vcs_info_msg_0_}'</tt> directly in your prompt like
this, you will need to have the <tt>PROMPT_SUBST</tt> option enabled.
</p>
<p>Now call the <tt>vcs_info_printsys</tt> utility from the command line:
</p>
<div class="example">
<pre class="example">% vcs_info_printsys
## list of supported version control backends:
## disabled systems are prefixed by a hash sign (#)
bzr
cdv
cvs
darcs
fossil
git
hg
mtn
p4
svk
svn
tla
## flavours (cannot be used in the enable or disable styles; they
## are enabled and disabled with their master [git-svn -> git])
## they *can* be used in contexts: ':vcs_info:git-svn:*'.
git-p4
git-svn
hg-git
hg-hgsubversion
hg-hgsvn
</pre></div>
<p>You may not want all of these because there is no point in running the
code to detect systems you do not use. So there is a way to disable
some backends altogether:
</p>
<div class="example">
<pre class="example">zstyle ':vcs_info:*' disable bzr cdv darcs mtn svk tla
</pre></div>
<p>You may also pick a few from that list and enable only those:
</p>
<div class="example">
<pre class="example">zstyle ':vcs_info:*' enable git cvs svn
</pre></div>
<p>If you rerun <tt>vcs_info_printsys</tt> after one of these commands, you will
see the backends listed in the <tt>disable</tt> style (or backends not in the
<tt>enable</tt> style - if you used that) marked as disabled by a hash sign.
That means the detection of these systems is skipped <em>completely</em>. No
wasted time there.
</p>
<hr>
<a name="Configuration-2"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Quickstart" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Oddities" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.2 Configuration</h3>
<p>The <tt>vcs_info</tt> feature can be configured via <tt>zstyle</tt>.
</p>
<p>First, the context in which we are working:
</p><div class="example">
<pre class="example">:vcs_info:<var>vcs-string</var>:<var>user-context</var>:<var>repo-root-name</var>
</pre></div>
<dl compact="compact">
<dt><var>vcs-string</var></dt>
<dd><p>is one of: <cite>git</cite>, <cite>git-svn</cite>, <cite>git-p4</cite>, <cite>hg</cite>, <cite>hg-git</cite>,
<cite>hg-hgsubversion</cite>, <cite>hg-hgsvn</cite>, <cite>darcs</cite>, <cite>bzr</cite>, <cite>cdv</cite>, <cite>mtn</cite>,
<cite>svn</cite>, <cite>cvs</cite>, <cite>svk</cite>, <cite>tla</cite>, <cite>p4</cite> or <cite>fossil</cite>. When hooks are
active the hooks name is added after a ‘+’. (See <cite>Hooks in vcs_info</cite>
below.)
</p>
</dd>
<dt><var>user-context</var></dt>
<dd><p>is a freely configurable string, assignable by
the user as the first argument to <tt>vcs_info</tt> (see its description
below).
</p>
</dd>
<dt><var>repo-root-name</var></dt>
<dd><p>is the name of a repository in which you want a
style to match. So, if you want a setting specific to <tt>/usr/src/zsh</tt>,
with that being a CVS checkout, you can set <var>repo-root-name</var> to
<tt>zsh</tt> to make it so.
</p>
</dd>
</dl>
<p>There are three special values for <var>vcs-string</var>: The first is named
<tt>-init-</tt>, that is in effect as long as there was no decision what VCS
backend to use. The second is <tt>-preinit-</tt>; it is used <em>before</em>
<tt>vcs_info</tt> is run, when initializing the data exporting variables. The
third special value is <tt>formats</tt> and is used by the <tt>vcs_info_lastmsg</tt>
for looking up its styles.
</p>
<p>The initial value of <var>repo-root-name</var> is <tt>-all-</tt> and it is replaced
with the actual name, as soon as it is known. Only use this part of the
context for defining the <tt>formats</tt>, <tt>actionformats</tt> or
<tt>branchformat</tt> styles, as it is guaranteed that <var>repo-root-name</var> is
set up correctly for these only. For all other styles, just use <tt>'*'</tt>
instead.
</p>
<p>There are two pre-defined values for <var>user-context</var>:
</p><dl compact="compact">
<dt><tt>default</tt></dt>
<dd><p>the one used if none is specified
</p></dd>
<dt><tt>command</tt></dt>
<dd><p>used by vcs_info_lastmsg to lookup its styles
</p></dd>
</dl>
<p>You can of course use <tt>':vcs_info:*'</tt> to match all VCSs in all
user-contexts at once.
</p>
<p>This is a description of all styles that are looked up.
</p>
<dl compact="compact">
<dd><a name="index-formats"></a>
</dd>
<dt><tt>formats</tt></dt>
<dd><p>A list of formats, used when actionformats is not used
(which is most of the time).
</p>
<a name="index-actionformats"></a>
</dd>
<dt><tt>actionformats</tt></dt>
<dd><p>A list of formats, used if there is a special
action going on in your current repository; like an interactive rebase or
a merge conflict.
</p>
<a name="index-branchformat"></a>
</dd>
<dt><tt>branchformat</tt></dt>
<dd><p>Some backends replace <tt>%b</tt> in the formats and
actionformats styles above, not only by a branch name but also by a
revision number. This style lets you modify how that string should look.
</p>
<a name="index-nvcsformats"></a>
</dd>
<dt><tt>nvcsformats</tt></dt>
<dd><p>These "formats" are set when we didn’t detect a version control system
for the current directory or <tt>vcs_info</tt> was disabled. This is useful if
you want <tt>vcs_info</tt> to completely take over the generation of your
prompt. You would do something like <tt>PS1='${vcs_info_msg_0_}'</tt> to
accomplish that.
</p>
<a name="index-hgrevformat"></a>
</dd>
<dt><tt>hgrevformat</tt></dt>
<dd><p><tt>hg</tt> uses both a hash and a revision number to reference a specific
changeset in a repository. With this style you can format the revision
string (see <tt>branchformat</tt>) to include either or both. It’s only
useful when <tt>get-revision</tt> is true. Note, the full 40-character revision id
is not available (except when using the <tt>use-simple</tt> option) because
executing hg more than once per prompt is too slow; you may customize this
behavior using hooks.
</p>
<a name="index-max_002dexports"></a>
</dd>
<dt><tt>max-exports</tt></dt>
<dd><p>Defines the maximum number of
<tt>vcs_info_msg_*_</tt> variables <tt>vcs_info</tt> will set.
</p>
<a name="index-enable-1"></a>
</dd>
<dt><tt>enable</tt></dt>
<dd><p>A list of backends you want to use. Checked in the <tt>-init-</tt> context. If
this list contains an item called <tt>NONE</tt> no backend is used at all and
<tt>vcs_info</tt> will do nothing. If this list contains <tt>ALL</tt>, <tt>vcs_info</tt>
will use all known backends. Only with <tt>ALL</tt> in <tt>enable</tt> will the
<tt>disable</tt> style have any effect. <tt>ALL</tt> and <tt>NONE</tt> are case insensitive.
</p>
<a name="index-disable-1"></a>
</dd>
<dt><tt>disable</tt></dt>
<dd><p>A list of VCSs you don’t want <tt>vcs_info</tt> to test for
repositories (checked in the <tt>-init-</tt> context, too). Only used if
<tt>enable</tt> contains <tt>ALL</tt>.
</p>
<a name="index-disable_002dpatterns"></a>
</dd>
<dt><tt>disable-patterns</tt></dt>
<dd><p>A list of patterns that are checked against <tt>$PWD</tt>. If a pattern
matches, <tt>vcs_info</tt> will be disabled. This style is checked in the
<tt>:vcs_info:-init-:*:-all-</tt> context.
</p>
<p>Say, <tt>~/.zsh</tt> is a directory under version control, in which you do
not want <tt>vcs_info</tt> to be active, do:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*' disable-patterns "$HOME/.zsh(|/*)"
</pre></div>
<a name="index-use_002dquilt"></a>
</dd>
<dt><tt>use-quilt</tt></dt>
<dd><p>If enabled, the <tt>quilt</tt> support code is active in ‘addon’ mode.
See <tt>Quilt Support</tt> for details.
</p>
<a name="index-quilt_002dstandalone"></a>
</dd>
<dt><tt>quilt-standalone</tt></dt>
<dd><p>If enabled, ‘standalone’ mode detection is attempted if no VCS is active
in a given directory. See <tt>Quilt Support</tt> for details.
</p>
<a name="index-quilt_002dpatch_002ddir"></a>
</dd>
<dt><tt>quilt-patch-dir</tt></dt>
<dd><p>Overwrite the value of the <tt>$QUILT_PATCHES</tt> environment variable. See
<tt>Quilt Support</tt> for details.
</p>
<a name="index-quiltcommand"></a>
</dd>
<dt><tt>quiltcommand</tt></dt>
<dd><p>When <tt>quilt</tt> itself is called in quilt support the value of this style
is used as the command name.
</p>
<a name="index-check_002dfor_002dchanges"></a>
</dd>
<dt><tt>check-for-changes</tt></dt>
<dd><p>If enabled, this style causes the <tt>%c</tt> and <tt>%u</tt> format escapes to show
when the working directory has uncommitted changes. The strings displayed by
these escapes can be controlled via the <tt>stagedstr</tt> and <tt>unstagedstr</tt>
styles. The only backends that currently support this option are <tt>git</tt>,
<tt>hg</tt>, and <tt>bzr</tt> (the latter two only support unstaged).
</p>
<p>For this style to be evaluated with the <tt>hg</tt> backend, the <tt>get-revision</tt>
style needs to be set and the <tt>use-simple</tt> style needs to be unset. The
latter is the default; the former is not.
</p>
<p>With the <tt>bzr</tt> backend, <em>lightweight checkouts</em> only honor this style if
the <tt>use-server</tt> style is set.
</p>
<p>Note, the actions taken if this style is enabled are potentially expensive
(read: they may be slow, depending on how big the current repository is).
Therefore, it is disabled by default.
</p>
<a name="index-check_002dfor_002dstaged_002dchanges"></a>
</dd>
<dt><tt>check-for-staged-changes</tt></dt>
<dd><p>This style is like <tt>check-for-changes</tt>, but it never checks the worktree
files, only the metadata in the <tt>.${vcs}</tt> dir. Therefore,
this style initializes only the <tt>%c</tt> escape (with <tt>stagedstr</tt>) but
not the <tt>%u</tt> escape. This style is faster than <tt>check-for-changes</tt>.
</p>
<p>In the <tt>git</tt> backend, this style checks for changes in the index.
Other backends do not currently implement this style.
</p>
<p>This style is disabled by default.
</p>
<a name="index-stagedstr"></a>
</dd>
<dt><tt>stagedstr</tt></dt>
<dd><p>This string will be used in the <tt>%c</tt> escape if there are staged changes in
the repository.
</p>
<a name="index-unstagedstr"></a>
</dd>
<dt><tt>unstagedstr</tt></dt>
<dd><p>This string will be used in the <tt>%u</tt> escape if there are unstaged changes
in the repository.
</p>
<a name="index-command-2"></a>
</dd>
<dt><tt>command</tt></dt>
<dd><p>This style causes <tt>vcs_info</tt> to use the supplied string as the command
to use as the VCS’s binary. Note, that setting this in ’<tt>:vcs_info:*</tt>’ is
not a good idea.
</p>
<p>If the value of this style is empty (which is the default), the used binary
name is the name of the backend in use (e.g. <tt>svn</tt> is used in an <tt>svn</tt>
repository).
</p>
<p>The <tt>repo-root-name</tt> part in the context is always the default <tt>-all-</tt>
when this style is looked up.
</p>
<p>For example, this style can be used to use binaries from non-default
installation directories. Assume, <tt>git</tt> is installed in /usr/bin but
your sysadmin installed a newer version in /usr/local/bin. Instead of
changing the order of your <tt>$PATH</tt> parameter, you can do this:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:git:*:-all-' command /usr/local/bin/git
</pre></div>
<a name="index-use_002dserver"></a>
</dd>
<dt><tt>use-server</tt></dt>
<dd><p>This is used by the Perforce backend (<tt>p4</tt>) to decide if it should
contact the Perforce server to find out if a directory is managed
by Perforce. This is the only reliable way of doing this, but runs
the risk of a delay if the server name cannot be found. If the
server (more specifically, the <tt>host</tt><tt>:</tt><tt>port</tt> pair describing the
server) cannot be contacted, its name is put into the associative array
<tt>vcs_info_p4_dead_servers</tt> and is not contacted again during the session
until it is removed by hand. If you do not set this style, the <tt>p4</tt>
backend is only usable if you have set the environment variable
<tt>P4CONFIG</tt> to a file name and have corresponding files in the root
directories of each Perforce client. See comments in the function
<tt>VCS_INFO_detect_p4</tt> for more detail.
</p>
<p>The Bazaar backend (<tt>bzr</tt>) uses this to permit contacting the server
about lightweight checkouts, see the <tt>check-for-changes</tt> style.
</p>
<a name="index-use_002dsimple"></a>
</dd>
<dt><tt>use-simple</tt></dt>
<dd><p>If there are two different ways of gathering
information, you can select the simpler one by setting this style to true;
the default is to use the not-that-simple code, which is potentially a lot
slower but might be more accurate in all possible cases. This style is
used by the <tt>bzr</tt> and <tt>hg</tt> backends. In the case of <tt>hg</tt> it will invoke
the external hexdump program to parse the binary dirstate cache file; this
method will not return the local revision number.
</p>
<a name="index-get_002drevision"></a>
</dd>
<dt><tt>get-revision</tt></dt>
<dd><p>If set to true, vcs_info goes the extra mile to figure out the revision of
a repository’s work tree (currently for the <tt>git</tt> and <tt>hg</tt> backends,
where this kind of information is not always vital). For <tt>git</tt>, the
hash value of the currently checked out commit is available via the <tt>%i</tt>
expansion. With <tt>hg</tt>, the local revision number and the corresponding
global hash are available via <tt>%i</tt>.
</p>
<a name="index-get_002dmq"></a>
</dd>
<dt><tt>get-mq</tt></dt>
<dd><p>If set to true, the <tt>hg</tt> backend will look for a Mercurial Queue (<tt>mq</tt>)
patch directory. Information will be available via the ‘<tt>%m</tt>’ replacement.
</p>
<a name="index-get_002dbookmarks"></a>
</dd>
<dt><tt>get-bookmarks</tt></dt>
<dd><p>If set to true, the <tt>hg</tt> backend will try to get a list of current
bookmarks. They will be available via the ‘<tt>%m</tt>’ replacement.
</p>
<p>The default is to generate a comma-separated list of all bookmark names
that refer to the currently checked out revision. If a bookmark is active,
its name is suffixed an asterisk and placed first in the list.
</p>
<a name="index-use_002dprompt_002descapes"></a>
</dd>
<dt><tt>use-prompt-escapes</tt></dt>
<dd><p>Determines if we assume that the assembled
string from <tt>vcs_info</tt> includes prompt escapes. (Used by
<tt>vcs_info_lastmsg</tt>.)
</p>
<a name="index-debug"></a>
</dd>
<dt><tt>debug</tt></dt>
<dd><p>Enable debugging output to track possible problems. Currently this style
is only used by <tt>vcs_info</tt>’s hooks system.
</p>
<a name="index-hooks"></a>
</dd>
<dt><tt>hooks</tt></dt>
<dd><p>A list style that defines hook-function names. See <cite>Hooks in vcs_info</cite>
below for details.
</p>
<a name="index-patch_002dformat"></a>
<a name="index-nopatch_002dformat"></a>
</dd>
<dt><tt>patch-format</tt></dt>
<dt><tt>nopatch-format</tt></dt>
<dd><p>This pair of styles format the patch information used by the <tt>%m</tt> expando in
formats and actionformats for the <tt>git</tt> and <tt>hg</tt> backends. The value is
subject to certain <tt>%</tt>-expansions described below.
</p>
<a name="index-get_002dunapplied"></a>
</dd>
<dt><tt>get-unapplied</tt></dt>
<dd><p>This boolean style controls whether a backend should attempt to gather a list
of unapplied patches (for example with Mercurial Queue patches).
</p>
<p>Used by the <tt>quilt</tt> and <tt>hg</tt> backends.
</p>
</dd>
</dl>
<p>The default values for these styles in all contexts are:
</p>
<dl compact="compact">
<dt><tt>formats</tt></dt>
<dd><p>" (%s)-[%b]%u%c-"
</p></dd>
<dt><tt>actionformats</tt></dt>
<dd><p>" (%s)-[%b|%a]%u%c-"
</p></dd>
<dt><tt>branchformat</tt></dt>
<dd><p>"%b:%r" (for bzr, svn, svk and hg)
</p></dd>
<dt><tt>nvcsformats</tt></dt>
<dd><p>""
</p></dd>
<dt><tt>hgrevformat</tt></dt>
<dd><p>"%r:%h"
</p></dd>
<dt><tt>max-exports</tt></dt>
<dd><p>2
</p></dd>
<dt><tt>enable</tt></dt>
<dd><p>ALL
</p></dd>
<dt><tt>disable</tt></dt>
<dd><p>(empty list)
</p></dd>
<dt><tt>disable-patterns</tt></dt>
<dd><p>(empty list)
</p></dd>
<dt><tt>check-for-changes</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>check-for-staged-changes</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>stagedstr</tt></dt>
<dd><p>(string: "S")
</p></dd>
<dt><tt>unstagedstr</tt></dt>
<dd><p>(string: "U")
</p></dd>
<dt><tt>command</tt></dt>
<dd><p>(empty string)
</p></dd>
<dt><tt>use-server</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>use-simple</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>get-revision</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>get-mq</tt></dt>
<dd><p>true
</p></dd>
<dt><tt>get-bookmarks</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>use-prompt-escapes</tt></dt>
<dd><p>true
</p></dd>
<dt><tt>debug</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>hooks</tt></dt>
<dd><p>(empty list)
</p></dd>
<dt><tt>use-quilt</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>quilt-standalone</tt></dt>
<dd><p>false
</p></dd>
<dt><tt>quilt-patch-dir</tt></dt>
<dd><p>empty - use <tt>$QUILT_PATCHES</tt>
</p></dd>
<dt><tt>quiltcommand</tt></dt>
<dd><p>quilt
</p></dd>
<dt><tt>patch-format</tt></dt>
<dd><p><var>backend dependent</var>
</p></dd>
<dt><tt>nopatch-format</tt></dt>
<dd><p><var>backend dependent</var>
</p></dd>
<dt><tt>get-unapplied</tt></dt>
<dd><p>false
</p></dd>
</dl>
<p>In normal <tt>formats</tt> and <tt>actionformats</tt> the following replacements are
done:
</p>
<dl compact="compact">
<dt><tt>%s</tt></dt>
<dd><p>The VCS in use (git, hg, svn, etc.).
</p></dd>
<dt><tt>%b</tt></dt>
<dd><p>Information about the current branch.
</p></dd>
<dt><tt>%a</tt></dt>
<dd><p>An identifier that describes the action. Only makes sense in
<tt>actionformats</tt>.
</p></dd>
<dt><tt>%i</tt></dt>
<dd><p>The current revision number or identifier. For <tt>hg</tt>
the <tt>hgrevformat</tt> style may be used to customize the output.
</p></dd>
<dt><tt>%c</tt></dt>
<dd><p>The string from the <tt>stagedstr</tt> style if there are staged
changes in the repository.
</p></dd>
<dt><tt>%u</tt></dt>
<dd><p>The string from the <tt>unstagedstr</tt> style if there are
unstaged changes in the repository.
</p></dd>
<dt><tt>%R</tt></dt>
<dd><p>The base directory of the repository.
</p></dd>
<dt><tt>%r</tt></dt>
<dd><p>The repository name. If <tt>%R</tt> is <tt>/foo/bar/repoXY</tt>, <tt>%r</tt>
is <tt>repoXY</tt>.
</p></dd>
<dt><tt>%S</tt></dt>
<dd><p>A subdirectory within a repository. If <tt>$PWD</tt> is
<tt>/foo/bar/repoXY/beer/tasty</tt>, <tt>%S</tt> is <tt>beer/tasty</tt>.
</p></dd>
</dl>
<dl compact="compact">
<dt><tt>%m</tt></dt>
<dd><p>A "misc" replacement. It is at the discretion of the backend to
decide what this replacement expands to.
</p>
<p>The <tt>hg</tt> and <tt>git</tt> backends use this expando to display patch information.
<tt>hg</tt> sources patch information from the <tt>mq</tt> extensions; <tt>git</tt> from the
<tt>rebase</tt> command and from the and <tt>stgit</tt> extension. The <tt>patch-format</tt>
and <tt>nopatch-format</tt> styles control the generated string. The former is used
when at least one patch from the patch queue has been applied, and the latter
otherwise.
</p>
<p>The <tt>hg</tt> backend displays bookmark information in this expando (in addition
to <tt>mq</tt> information). See the <tt>get-mq</tt> and <tt>get-bookmarks</tt> styles. Both
of these styles may be enabled at the same time. If both are enabled, both
resulting strings will be shown separated by a semicolon (that cannot currently
be customized).
</p>
</dd>
</dl>
<p>In <tt>branchformat</tt> these replacements are done:
</p>
<dl compact="compact">
<dt><tt>%b</tt></dt>
<dd><p>The branch name.
</p></dd>
<dt><tt>%r</tt></dt>
<dd><p>The current revision number or the <tt>hgrevformat</tt> style for
<tt>hg</tt>.
</p></dd>
</dl>
<p>In <tt>hgrevformat</tt> these replacements are done:
</p>
<dl compact="compact">
<dt><tt>%r</tt></dt>
<dd><p>The current local revision number.
</p></dd>
<dt><tt>%h</tt></dt>
<dd><p>The current global revision identifier.
</p></dd>
</dl>
<p>In <tt>patch-format</tt> and <tt>nopatch-format</tt> these replacements are done:
</p>
<dl compact="compact">
<dt><tt>%p</tt></dt>
<dd><p>The name of the top-most applied patch (<tt>applied-string</tt>).
</p></dd>
<dt><tt>%u</tt></dt>
<dd><p>The number of unapplied patches (<tt>unapplied-string</tt>).
</p></dd>
<dt><tt>%n</tt></dt>
<dd><p>The number of applied patches.
</p></dd>
<dt><tt>%c</tt></dt>
<dd><p>The number of unapplied patches.
</p></dd>
<dt><tt>%a</tt></dt>
<dd><p>The number of all patches.
</p></dd>
<dt><tt>%g</tt></dt>
<dd><p>The names of active <tt>mq</tt> guards (<tt>hg</tt> backend).
</p></dd>
<dt><tt>%G</tt></dt>
<dd><p>The number of active <tt>mq</tt> guards (<tt>hg</tt> backend).
</p></dd>
</dl>
<p>Not all VCS backends have to support all replacements. For <tt>nvcsformats</tt>
no replacements are performed at all, it is just a string.
</p>
<hr>
<a name="Oddities"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Configuration-2" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Quilt-Support" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.3 Oddities</h3>
<p>If you want to use the <tt>%b</tt> (bold off) prompt expansion in <tt>formats</tt>,
which expands <tt>%b</tt> itself, use <tt>%%b</tt>. That will cause the <tt>vcs_info</tt>
expansion to replace <tt>%%b</tt> with <tt>%b</tt>, so that zsh’s prompt expansion
mechanism can handle it. Similarly, to hand down <tt>%b</tt> from
<tt>branchformat</tt>, use <tt>%%%%b</tt>. Sorry for this inconvenience, but it
cannot be easily avoided. Luckily we do not clash with a lot of prompt
expansions and this only needs to be done for those.
</p>
<hr>
<a name="Quilt-Support"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Oddities" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Function-Descriptions-_0028Public-API_0029" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.4 Quilt Support</h3>
<p><cite>Quilt</cite> is not a version control system, therefore this is not implemented
as a backend. It can help keeping track of a series of patches. People use it
to keep a set of changes they want to use on top of software packages (which
is tightly integrated into the package build process - the Debian project
does this for a large number of packages). Quilt can also help individual
developers keep track of their own patches on top of real version control
systems.
</p>
<p>The <tt>vcs_info</tt> integration tries to support both ways of using quilt by
having two slightly different modes of operation: ‘addon’ mode and
‘standalone’ mode).
</p>
<p>For ‘addon’ mode to become active <tt>vcs_info</tt> must have already detected a
real version control system controlling the directory. If that is the case,
a directory that holds quilt’s patches needs to be found. That directory is
configurable via the ‘<tt>QUILT_PATCHES</tt>’ environment variable. If that
variable exists its value is used, otherwise the value ‘<tt>patches</tt>’ is
assumed. The value from <tt>$QUILT_PATCHES</tt> can be overwritten using the
<tt>`quilt-patches'</tt> style. (Note: you can use <tt>vcs_info</tt> to keep the value
of <tt>$QUILT_PATCHES</tt> correct all the time via the <tt>post-quilt</tt> hook).
</p>
<p>When the directory in question is found, quilt is assumed to be active. To
gather more information, <tt>vcs_info</tt> looks for a directory called ‘.pc’;
Quilt uses that directory to track its current state. If this directory does
not exist we know that quilt has not done anything to the working directory
(read: no patches have been applied yet).
</p>
<p>If patches are applied, <tt>vcs_info</tt> will try to find out which. If you want
to know which patches of a series are not yet applied, you need to activate
the <tt>get-unapplied</tt> style in the appropriate context.
</p>
<p><tt>vcs_info</tt> allows for very detailed control over how the gathered
information is presented (see the below sections, <cite>Styles</cite> and <cite>Hooks in
vcs_info</cite>), all of which are documented below. Note there are a number of
other patch tracking systems that work on top of a certain version control
system (like <tt>stgit</tt> for <cite>git</cite>, or <tt>mq</tt> for <cite>hg</cite>); the configuration
for systems like that are generally configured the same way as the <cite>quilt</cite>
support.
</p>
<p>If the <cite>quilt</cite> support is working in ‘addon’ mode, the produced string is
available as a simple format replacement (<tt>%Q</tt> to be precise), which can
be used in <tt>formats</tt> and <tt>actionformats</tt>; see below for details).
</p>
<p>If, on the other hand, the support code is working in ‘standalone’ mode,
<tt>vcs_info</tt> will pretend as if <tt>quilt</tt> were an actual version control
system. That means that the version control system identifier (which
otherwise would be something like ‘svn’ or ‘cvs’) will be set to
‘<tt>-quilt-</tt>’. This has implications on the used style context where this
identifier is the second element. <tt>vcs_info</tt> will have filled in a proper
value for the "repository’s" root directory and the string containing the
information about quilt’s state will be available as the ‘misc’ replacement
(and <tt>%Q</tt> for compatibility with ‘addon’ mode.
</p>
<p>What is left to discuss is how ‘standalone’ mode is detected. The detection
itself is a series of searches for directories. You can have this detection
enabled all the time in every directory that is not otherwise under version
control. If you know there is only a limited set of trees where you would
like <tt>vcs_info</tt> to try and look for Quilt in ‘standalone’ mode to minimise
the amount of searching on every call to <tt>vcs_info</tt>, there are a number of
ways to do that:
</p>
<p>Essentially, ‘standalone’ mode detection is controlled by a style called
‘<tt>quilt-standalone</tt>’. It is a string style and its value can have different
effects. The simplest values are: ‘<tt>always</tt>’ to run detection every time
<tt>vcs_info</tt> is run, and ‘<tt>never</tt>’ to turn the detection off entirely.
</p>
<p>If the value of <tt>quilt-standalone</tt> is something else, it is interpreted
differently. If the value is the name of a scalar variable the value of that
variable is checked and that value is used in the same ‘always’/‘never’ way
as described above.
</p>
<p>If the value of <tt>quilt-standalone</tt> is an array, the elements of that array
are used as directory names under which you want the detection to be active.
</p>
<p>If <tt>quilt-standalone</tt> is an associative array, the keys are taken as
directory names under which you want the detection to be active, but only if
the corresponding value is the string ‘<tt>true</tt>’.
</p>
<p>Last, but not least, if the value of <tt>quilt-standalone</tt> is the name of a
function, the function is called without arguments and the return value
decides whether detection should be active. A ‘0’ return value is true; a
non-zero return value is interpreted as false.
</p>
<p>Note, if there is both a function and a variable by the name of
<tt>quilt-standalone</tt>, the function will take precedence.
</p>
<hr>
<a name="Function-Descriptions-_0028Public-API_0029"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Quilt-Support" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Variable-Description" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.5 Function Descriptions (Public API)</h3>
<dl compact="compact">
<dd><a name="index-vcs_005finfo"></a>
</dd>
<dt><tt>vcs_info</tt> [<var>user-context</var>]</dt>
<dd><p>The main function, that runs all backends and assembles all data into
<tt>${vcs_info_msg_*_}</tt>. This is the function you want to call from
<tt>precmd</tt> if you want to include up-to-date information in your prompt (see
<tt>Variable description</tt> below). If an argument is given, that string will be
used instead of <tt>default</tt> in the <var>user-context</var> field of the style
context.
</p>
<a name="index-vcs_005finfo_005fhookadd"></a>
</dd>
<dt><tt>vcs_info_hookadd</tt></dt>
<dd><p>Statically registers a number of functions to a given hook. The hook needs
to be given as the first argument; what follows is a list of hook-function
names to register to the hook. The ‘<tt>+vi-</tt>’ prefix needs to be left out
here. See <cite>Hooks in vcs_info</cite> below for details.
</p>
<a name="index-vcs_005finfo_005fhookdel"></a>
</dd>
<dt><tt>vcs_info_hookdel</tt></dt>
<dd><p>Remove hook-functions from a given hook. The hook needs to be given as the
first non-option argument; what follows is a list of hook-function
names to un-register from the hook. If ‘<tt>-a</tt>’ is used as the first
argument, <tt>all</tt> occurrences of the functions are unregistered. Otherwise
only the last occurrence is removed (if a function was registered to a hook
more than once) . The ‘<tt>+vi-</tt>’ prefix needs to be left out here. See
<cite>Hooks in vcs_info</cite> below for details.
</p>
<a name="index-vcs_005finfo_005flastmsg"></a>
</dd>
<dt><tt>vcs_info_lastmsg</tt></dt>
<dd><p>Outputs the last <tt>${vcs_info_msg_*_}</tt> value.
Takes into account the value of the <tt>use-prompt-escapes</tt> style in
<tt>':vcs_info:formats:command:-all-'</tt>. It also only prints <tt>max-exports</tt>
values.
</p>
<a name="index-vcs_005finfo_005fprintsys"></a>
</dd>
<dt><tt>vcs_info_printsys</tt> [<var>user-context</var>]</dt>
<dd><p>Prints a list of all
supported version control systems. Useful to find out possible contexts
(and which of them are enabled) or values for the <tt>disable</tt> style.
</p>
<a name="index-vcs_005finfo_005fsetsys"></a>
</dd>
<dt><tt>vcs_info_setsys</tt></dt>
<dd><p>Initializes <tt>vcs_info</tt>’s internal list of
available backends. With this function, you can add support for new VCSs
without restarting the shell.
</p>
</dd>
</dl>
<p>All functions named <tt>VCS_INFO_*</tt> are for internal use only.
</p>
<hr>
<a name="Variable-Description"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Function-Descriptions-_0028Public-API_0029" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Hooks-in-vcs_005finfo" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.6 Variable Description</h3>
<dl compact="compact">
<dt><tt>${vcs_info_msg_</tt><var>N</var><tt>_}</tt> (Note the trailing underscore)</dt>
<dd><p>Where <var>N</var> is an integer, e.g., <tt>vcs_info_msg_0_</tt>. These variables
are the storage for the informational message the last <tt>vcs_info</tt> call
has assembled. These are strongly connected to the <tt>formats</tt>,
<tt>actionformats</tt> and <tt>nvcsformats</tt> styles described above. Those styles
are lists. The first member of that list gets expanded into
<tt>${vcs_info_msg_0_}</tt>, the second into <tt>${vcs_info_msg_1_}</tt>
and the Nth into <tt>${vcs_info_msg_N-1_}</tt>. (See the <tt>max-exports</tt>
style above.)
</p>
</dd>
</dl>
<p>All variables named <tt>VCS_INFO_*</tt> are for internal use only.
</p>
<hr>
<a name="Hooks-in-vcs_005finfo"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Variable-Description" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Examples-1" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.7 Hooks in vcs_info</h3>
<p>Hooks are places in <tt>vcs_info</tt> where you can run your own code. That
code can communicate with the code that called it and through that,
change the system’s behaviour.
</p>
<p>For configuration, hooks change the style context:
</p><div class="example">
<pre class="example">:vcs_info:<var>vcs-string</var>+<var>hook-name</var>:<var>user-context</var>:<var>repo-root-name</var>
</pre></div>
<p>To register functions to a hook, you need to list them in the <tt>hooks</tt>
style in the appropriate context.
</p>
<p>Example:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*+foo:*' hooks bar baz
</pre></div>
<p>This registers functions to the hook ‘foo’ for all backends. In order to
avoid namespace problems, all registered function names are prepended by
a ‘<tt>+vi-</tt>’, so the actual functions called for the ‘foo’ hook are
‘<tt>+vi-bar</tt>’ and ‘<tt>+vi-baz</tt>’.
</p>
<p>If you would like to register a function to a hook regardless of the
current context, you may use the <tt>vcs_info_hookadd</tt> function. To remove
a function that was added like that, the <tt>vcs_info_hookdel</tt> function
can be used.
</p>
<p>If something seems weird, you can enable the ‘debug’ boolean style in
the proper context and the hook-calling code will print what it tried
to execute and whether the function in question existed.
</p>
<p>When you register more than one function to a hook, all functions are
executed one after another until one function returns non-zero or until
all functions have been called. Context-sensitive hook functions are
executed <tt>before</tt> statically registered ones (the ones added by
<tt>vcs_info_hookadd</tt>).
</p>
<p>You may pass data between functions via an associative array, <tt>user_data</tt>.
For example:
</p><div class="example">
<pre class="example">
+vi-git-myfirsthook(){
user_data[myval]=$myval
}
+vi-git-mysecondhook(){
# do something with ${user_data[myval]}
}
</pre></div>
<p>There are a number of variables that are special in hook contexts:
</p>
<dl compact="compact">
<dt><tt>ret</tt></dt>
<dd><p>The return value that the hooks system will return to the caller. The
default is an integer ‘zero’. If and how a changed <tt>ret</tt> value changes
the execution of the caller depends on the specific hook. See the hook
documentation below for details.
</p>
</dd>
<dt><tt>hook_com</tt></dt>
<dd><p>An associated array which is used for bidirectional communication from
the caller to hook functions. The used keys depend on the specific hook.
</p>
</dd>
<dt><tt>context</tt></dt>
<dd><p>The active context of the hook. Functions that wish to change this
variable should make it local scope first.
</p>
</dd>
<dt><tt>vcs</tt></dt>
<dd><p>The current VCS after it was detected. The same values as in the
enable/disable style are used. Available in all hooks except <tt>start-up</tt>.
</p>
</dd>
</dl>
<p>Finally, the full list of currently available hooks:
</p>
<dl compact="compact">
<dt><tt>start-up</tt></dt>
<dd><p>Called after starting <tt>vcs_info</tt> but before the VCS in this directory is
determined. It can be used to deactivate <tt>vcs_info</tt> temporarily if
necessary. When <tt>ret</tt> is set to <tt>1</tt>, <tt>vcs_info</tt> aborts and does
nothing; when set to <tt>2</tt>, <tt>vcs_info</tt> sets up everything as if no
version control were active and exits.
</p>
</dd>
<dt><tt>pre-get-data</tt></dt>
<dd><p>Same as <tt>start-up</tt> but after the VCS was detected.
</p>
</dd>
<dt><tt>gen-hg-bookmark-string</tt></dt>
<dd><p>Called in the Mercurial backend when a bookmark string is generated; the
<tt>get-revision</tt> and <tt>get-bookmarks</tt> styles must be true.
</p>
<p>This hook gets the names of the Mercurial bookmarks that
<tt>vcs_info</tt> collected from ‘hg’.
</p>
<p>If a bookmark is active, the key <tt>${hook_com[hg-active-bookmark]}</tt> is
set to its name. The key is otherwise unset.
</p>
<p>When setting <tt>ret</tt> to non-zero, the string in
<tt>${hook_com[hg-bookmark-string]}</tt> will be used in the <tt>%m</tt> escape in
<tt>formats</tt> and <tt>actionformats</tt> and will be available in the global
<tt>backend_misc</tt> array as <tt>${backend_misc[bookmarks]}</tt>.
</p>
</dd>
<dt><tt>gen-applied-string</tt></dt>
<dd><p>Called in the <tt>git</tt> (with <tt>stgit</tt> or during rebase or merge), and <tt>hg</tt>
(with <tt>mq</tt>) backends and in <tt>quilt</tt> support when the <tt>applied-string</tt>
is generated; the <tt>use-quilt</tt> zstyle must be true for <tt>quilt</tt> (the <tt>mq</tt>
and <tt>stgit</tt> backends are active by default).
</p>
<p>This hook gets the names of all applied patches which <tt>vcs_info</tt> collected
so far in the opposite order, which means that the first argument is the
top-most patch and so forth.
</p>
<p>When setting <tt>ret</tt> to non-zero, the string in
<tt>${hook_com[applied-string]}</tt> will be used in the <tt>%m</tt> escape in
<tt>formats</tt> and <tt>actionformats</tt>; it will be available in the global
<tt>backend_misc</tt> array as <tt>$backend_misc[patches]}</tt>; and it will be
available as <tt>%p</tt> in the <tt>patch-format</tt> and <tt>nopatch-format</tt> styles.
</p>
</dd>
<dt><tt>gen-unapplied-string</tt></dt>
<dd><p>Called in the <tt>git</tt> (with <tt>stgit</tt> or during rebase), and <tt>hg</tt> (with
<tt>mq</tt>) backend and in <tt>quilt</tt> support when the <tt>unapplied-string</tt> is
generated; the <tt>get-unapplied</tt> style must be true.
</p>
<p>This hook gets the names of all unapplied patches which <tt>vcs_info</tt>
collected so far in the opposite order, which mean that the first argument is
the patch next-in-line to be applied and so forth.
</p>
<p>When setting <tt>ret</tt> to non-zero, the string in
<tt>${hook_com[unapplied-string]}</tt> will be available as <tt>%u</tt> in the
<tt>patch-format</tt> and <tt>nopatch-format</tt> styles.
</p>
</dd>
<dt><tt>gen-mqguards-string</tt></dt>
<dd><p>Called in the <tt>hg</tt> backend when <tt>guards-string</tt> is generated; the
<tt>get-mq</tt> style must be true (default).
</p>
<p>This hook gets the names of any active <tt>mq</tt> guards.
</p>
<p>When setting <tt>ret</tt> to non-zero, the string in
<tt>${hook_com[guards-string]}</tt> will be used in the <tt>%g</tt> escape in the
<tt>patch-format</tt> and <tt>nopatch-format</tt> styles.
</p>
</dd>
<dt><tt>no-vcs</tt></dt>
<dd><p>This hooks is called when no version control system was detected.
</p>
<p>The ‘<tt>hook_com</tt>’ parameter is not used.
</p>
</dd>
<dt><tt>post-backend</tt></dt>
<dd><p>Called as soon as the backend has finished collecting information.
</p>
<p>The ‘<tt>hook_com</tt>’ keys available are as for the <tt>set-message</tt> hook.
</p>
</dd>
<dt><tt>post-quilt</tt></dt>
<dd><p>Called after the <tt>quilt</tt> support is done. The following information
is passed as arguments to the hook: 1. the quilt-support mode (‘addon’ or
‘standalone’); 2. the directory that contains the patch series; 3. the
directory that holds quilt’s status information (the ‘.pc’ directory) or
the string <tt>"-nopc-"</tt> if that directory wasn’t found.
</p>
<p>The ‘hook_com’ parameter is not used.
</p>
</dd>
<dt><tt>set-branch-format</tt></dt>
<dd><p>Called before ‘<tt>branchformat</tt>’ is set. The only argument to the
hook is the format that is configured at this point.
</p>
<p>The ‘<tt>hook_com</tt>’ keys considered are ‘<tt>branch</tt>’ and ‘<tt>revision</tt>’.
They are set to the values figured out so far by <tt>vcs_info</tt> and any
change will be used directly when the actual replacement is done.
</p>
<p>If <tt>ret</tt> is set to non-zero, the string in
<tt>${hook_com[branch-replace]}</tt> will be used unchanged as the
‘<tt>%b</tt>’ replacement in the variables set by <tt>vcs_info</tt>.
</p>
</dd>
<dt><tt>set-hgrev-format</tt></dt>
<dd><p>Called before a ‘<tt>hgrevformat</tt>’ is set. The only argument to the
hook is the format that is configured at this point.
</p>
<p>The ‘<tt>hook_com</tt>’ keys considered are ‘<tt>hash</tt>’ and ‘<tt>localrev</tt>’.
They are set to the values figured out so far by <tt>vcs_info</tt> and any
change will be used directly when the actual replacement is done.
</p>
<p>If <tt>ret</tt> is set to non-zero, the string in
<tt>${hook_com[rev-replace]}</tt> will be used unchanged as the
‘<tt>%i</tt>’ replacement in the variables set by <tt>vcs_info</tt>.
</p>
</dd>
<dt><tt>pre-addon-quilt</tt></dt>
<dd><p>This hook is used when <tt>vcs_info</tt>’s quilt functionality is active in "addon"
mode (quilt used on top of a real version control system). It is activated
right before any quilt specific action is taken.
</p>
<p>Setting the ‘<tt>ret</tt>’ variable in this hook to a non-zero value avoids any
quilt specific actions from being run at all.
</p>
</dd>
<dt><tt>set-patch-format</tt></dt>
<dd><p>This hook is used to control some of the possible expansions in
<tt>patch-format</tt> and <tt>nopatch-format</tt> styles with patch queue systems such as
quilt, mqueue and the like.
</p>
<p>This hook is used in the <tt>git</tt>, <tt>hg</tt> and <tt>quilt</tt> backends.
</p>
<p>The hook allows the control of the <tt>%p</tt> (<tt>${hook_com[applied]}</tt>) and <tt>%u</tt>
(<tt>${hook_com[unapplied]}</tt>) expansion in all backends that use the hook. With
the mercurial backend, the <tt>%g</tt> (<tt>${hook_com[guards]}</tt>) expansion is
controllable in addition to that.
</p>
<p>If <tt>ret</tt> is set to non-zero, the string in <tt>${hook_com[patch-replace]}</tt>
will be used unchanged instead of an expanded format from <tt>patch-format</tt> or
<tt>nopatch-format</tt>.
</p>
</dd>
<dt><tt>set-message</tt></dt>
<dd><p>Called each time before a ‘<tt>vcs_info_msg_</tt><var>N</var><tt>_</tt>’ message is set.
It takes two arguments; the first being the ‘<var>N</var>’ in the message
variable name, the second is the currently configured <tt>formats</tt> or
<tt>actionformats</tt>.
</p>
<p>There are a number of ‘<tt>hook_com</tt>’ keys, that are used here:
‘<tt>action</tt>’, ‘<tt>branch</tt>’, ‘<tt>base</tt>’, ‘<tt>base-name</tt>’, ‘<tt>subdir</tt>’,
‘<tt>staged</tt>’, ‘<tt>unstaged</tt>’, ‘<tt>revision</tt>’, ‘<tt>misc</tt>’, ‘<tt>vcs</tt>’
and one ‘<tt>miscN</tt>’ entry for each backend-specific data field (<tt>N</tt>
starting at zero). They are set to the values figured out so far by
<tt>vcs_info</tt> and any change will be used directly when the actual
replacement is done.
</p>
<p>Since this hook is triggered multiple times (once for each configured
<tt>formats</tt> or <tt>actionformats</tt>), each of the ‘<tt>hook_com</tt>’ keys mentioned
above (except for the <tt>miscN</tt> entries) has an ‘<tt>_orig</tt>’ counterpart,
so even if you changed a value to your liking you can still get the
original value in the next run. Changing the ‘<tt>_orig</tt>’ values is
probably not a good idea.
</p>
<p>If <tt>ret</tt> is set to non-zero, the string in
<tt>${hook_com[message]}</tt> will be used unchanged as the message by
<tt>vcs_info</tt>.
</p>
</dd>
</dl>
<p>If all of this sounds rather confusing, take a look at the <cite>Examples</cite>
section below and also in the <tt>Misc/vcs_info-examples</tt> file in the Zsh source.
They contain some explanatory code.
</p>
<hr>
<a name="Examples-1"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Hooks-in-vcs_005finfo" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Version-Control-Information" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Prompt-Themes" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.4.8 Examples</h3>
<p>Don’t use <tt>vcs_info</tt> at all (even though it’s in your prompt):
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*' enable NONE
</pre></div>
<p>Disable the backends for <tt>bzr</tt> and <tt>svk</tt>:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*' disable bzr svk
</pre></div>
<p>Disable everything <em>but</em> <tt>bzr</tt> and <tt>svk</tt>:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*' enable bzr svk
</pre></div>
<p>Provide a special formats for <tt>git</tt>:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:git:*' formats ' GIT, BABY! [%b]'
zstyle ':vcs_info:git:*' actionformats ' GIT ACTION! [%b|%a]'
</pre></div>
<p>All <tt>%x</tt> expansion in all sorts of formats (<tt>formats</tt>, <tt>actionformats</tt>,
<tt>branchformat</tt>, you name it) are done using the ‘<tt>zformat</tt>’ builtin from
the ‘<tt>zsh/zutil</tt>’ module. That means you can do everything with these
<tt>%x</tt> items what zformat supports. In particular, if you want something
that is really long to have a fixed width, like a hash in a mercurial
branchformat, you can do this: <tt>%12.12i</tt>. That’ll shrink the 40 character
hash to its 12 leading characters. The form is actually
‘<tt>%</tt><var>min</var><tt>.</tt><var>max</var><tt>x</tt>’. More is possible.
See <a href="Zsh-Modules.html#The-zsh_002fzutil-Module">The zsh/zutil Module</a> for details.
</p>
<p>Use the quicker <tt>bzr</tt> backend
</p><div class="example">
<pre class="example">zstyle ':vcs_info:bzr:*' use-simple true
</pre></div>
<p>If you do use <tt>use-simple</tt>, please report if it does ‘the-right-thing[tm]’.
</p>
<p>Display the revision number in yellow for <tt>bzr</tt> and <tt>svn</tt>:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:(svn|bzr):*' \
branchformat '%b%{'${fg[yellow]}'%}:%r'
</pre></div>
<p>If you want colors, make sure you enclose the color codes in <tt>%{</tt><var>...</var><tt>%}</tt>
if you want to use the string provided by <tt>vcs_info</tt> in prompts.
</p>
<p>Here is how to print the VCS information as a command (not in a prompt):
</p><div class="example">
<pre class="example">alias vcsi='vcs_info command; vcs_info_lastmsg'
</pre></div>
<p>This way, you can even define different formats for output via
<tt>vcs_info_lastmsg</tt> in the ’<tt>:vcs_info:*:command:*</tt>’ namespace.
</p>
<p>Now as promised, some code that uses hooks:
say, you’d like to replace the string ‘svn’ by ‘subversion’ in
<tt>vcs_info</tt>’s <tt>%s</tt> <tt>formats</tt> replacement.
</p>
<p>First, we will tell <tt>vcs_info</tt> to call a function when populating
the message variables with the gathered information:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*+set-message:*' hooks svn2subversion
</pre></div>
<p>Nothing happens. Which is reasonable, since we didn’t define the actual
function yet. To see what the hooks subsystem is trying to do, enable the
‘<tt>debug</tt>’ style:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*+*:*' debug true
</pre></div>
<p>That should give you an idea what is going on. Specifically, the function
that we are looking for is ‘<tt>+vi-svn2subversion</tt>’. Note, the ‘<tt>+vi-</tt>’
prefix. So, everything is in order, just as documented. When you are done
checking out the debugging output, disable it again:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:*+*:*' debug false
</pre></div>
<p>Now, let’s define the function:
</p><div class="example">
<pre class="example">
function +vi-svn2subversion() {
[[ ${hook_com[vcs_orig]} == svn ]] && hook_com[vcs]=subversion
}
</pre></div>
<p>Simple enough. And it could have even been simpler, if only we had
registered our function in a less generic context. If we do it only in
the ‘<tt>svn</tt>’ backend’s context, we don’t need to test which the active
backend is:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:svn+set-message:*' hooks svn2subversion
</pre></div>
<div class="example">
<pre class="example">
function +vi-svn2subversion() {
hook_com[vcs]=subversion
}
</pre></div>
<p>And finally a little more elaborate example, that uses a hook to create
a customised bookmark string for the <tt>hg</tt> backend.
</p>
<p>Again, we start off by registering a function:
</p><div class="example">
<pre class="example">zstyle ':vcs_info:hg+gen-hg-bookmark-string:*' hooks hgbookmarks
</pre></div>
<p>And then we define the ‘<tt>+vi-hgbookmarks</tt> function:
</p><div class="example">
<pre class="example">
function +vi-hgbookmarks() {
# The default is to connect all bookmark names by
# commas. This mixes things up a little.
# Imagine, there's one type of bookmarks that is
# special to you. Say, because it's *your* work.
# Those bookmarks look always like this: "sh/*"
# (because your initials are sh, for example).
# This makes the bookmarks string use only those
# bookmarks. If there's more than one, it
# concatenates them using commas.
# The bookmarks returned by `hg' are available in
# the function's positional parameters.
local s="${(Mj:,:)@:#sh/*}"
# Now, the communication with the code that calls
# the hook functions is done via the hook_com[]
# hash. The key at which the `gen-hg-bookmark-string'
# hook looks is `hg-bookmark-string'. So:
hook_com[hg-bookmark-string]=$s
# And to signal that we want to use the string we
# just generated, set the special variable `ret' to
# something other than the default zero:
ret=1
return 0
}
</pre></div>
<p>Some longer examples and code snippets which might be useful are available in
the examples file located at Misc/vcs_info-examples in the Zsh source
directory.
</p>
<p>This concludes our guided tour through zsh’s <tt>vcs_info</tt>.
</p>
<hr>
<a name="Prompt-Themes"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Examples-1" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Installation-3" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Prompt-Themes-1"></a>
<h2 class="section">26.5 Prompt Themes</h2>
<hr>
<a name="Installation-3"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Prompt-Themes" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Prompt-Themes" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Theme-Selection" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.5.1 Installation</h3>
<p>You should make sure all the functions from the <tt>Functions/Prompts</tt>
directory of the source distribution are available; they all begin with
the string ‘<tt>prompt_</tt>’ except for the special function‘<tt>promptinit</tt>’.
You also need the ‘<tt>colors</tt>’ function from <tt>Functions/Misc</tt>. All of
these functions may already have been installed on your system; if not,
you will need to find them and copy them. The directory should appear as
one of the elements of the <tt>fpath</tt> array (this should already be the
case if they were installed), and at least the function <tt>promptinit</tt>
should be autoloaded; it will autoload the rest. Finally, to initialize
the use of the system you need to call the <tt>promptinit</tt> function. The
following code in your <tt>.zshrc</tt> will arrange for this; assume the
functions are stored in the directory <tt>~/myfns</tt>:
</p>
<div class="example">
<pre class="example">fpath=(~/myfns $fpath)
autoload -U promptinit
promptinit
</pre></div>
<hr>
<a name="Theme-Selection"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation-3" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Prompt-Themes" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#ZLE-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.5.2 Theme Selection</h3>
<p>Use the <tt>prompt</tt> command to select your preferred theme. This command
may be added to your <tt>.zshrc</tt> following the call to <tt>promptinit</tt> in
order to start zsh with a theme already selected.
</p>
<dl compact="compact">
<dt><tt>prompt</tt> [ <tt>-c</tt> | <tt>-l</tt> ]</dt>
<dt><tt>prompt</tt> [ <tt>-p</tt> | <tt>-h</tt> ] [ <var>theme</var> ... ]</dt>
<dt><tt>prompt</tt> [ <tt>-s</tt> ] <var>theme</var> [ <var>arg</var> ... ]</dt>
<dd><p>Set or examine the prompt theme. With no options and a <var>theme</var>
argument, the theme with that name is set as the current theme. The
available themes are determined at run time; use the <tt>-l</tt> option to see
a list. The special <var>theme</var> ‘<tt>random</tt>’ selects at random one of the
available themes and sets your prompt to that.
</p>
<p>In some cases the <var>theme</var> may be modified by one or more arguments,
which should be given after the theme name. See the help for each theme
for descriptions of these arguments.
</p>
<p>Options are:
</p>
<dl compact="compact">
<dt><tt>-c</tt></dt>
<dd><p>Show the currently selected theme and its parameters, if any.
</p></dd>
<dt><tt>-l</tt></dt>
<dd><p>List all available prompt themes.
</p></dd>
<dt><tt>-p</tt></dt>
<dd><p>Preview the theme named by <var>theme</var>, or all themes if no
<var>theme</var> is given.
</p></dd>
<dt><tt>-h</tt></dt>
<dd><p>Show help for the theme named by <var>theme</var>, or for the
<tt>prompt</tt> function if no <var>theme</var> is given.
</p></dd>
<dt><tt>-s</tt></dt>
<dd><p>Set <var>theme</var> as the current theme and save state.
</p></dd>
</dl>
</dd>
<dt><tt>prompt_</tt><var>theme</var><tt>_setup</tt></dt>
<dd><p>Each available <var>theme</var> has a setup function which is called by the
<tt>prompt</tt> function to install that theme. This function may define
other functions as necessary to maintain the prompt, including functions
used to preview the prompt or provide help for its use. You should not
normally call a theme’s setup function directly.
</p>
</dd>
</dl>
<hr>
<a name="ZLE-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Theme-Selection" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Widgets-1" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="ZLE-Functions-1"></a>
<h2 class="section">26.6 ZLE Functions</h2>
<hr>
<a name="Widgets-1"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#ZLE-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#ZLE-Functions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Utility-Functions-1" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.6.1 Widgets</h3>
<p>These functions all implement user-defined ZLE widgets (see
<a href="Zsh-Line-Editor.html#Zsh-Line-Editor">Zsh Line Editor</a>) which can be bound to keystrokes in interactive shells. To use them,
your <tt>.zshrc</tt> should contain lines of the form
</p>
<div class="example">
<pre class="example">autoload <var>function</var>
zle -N <var>function</var>
</pre></div>
<p>followed by an appropriate <tt>bindkey</tt> command to associate the function
with a key sequence. Suggested bindings are described below.
</p>
<dl compact="compact">
<dt>bash-style word functions</dt>
<dd><p>If you are looking for functions to implement moving over and editing
words in the manner of bash, where only alphanumeric characters are
considered word characters, you can use the functions described in
the next section. The following is sufficient:
</p>
<div class="example">
<pre class="example">autoload -U select-word-style
select-word-style bash
</pre></div>
<a name="index-forward_002dword_002dmatch"></a>
<a name="index-backward_002dword_002dmatch"></a>
<a name="index-kill_002dword_002dmatch"></a>
<a name="index-backward_002dkill_002dword_002dmatch"></a>
<a name="index-transpose_002dwords_002dmatch"></a>
<a name="index-capitalize_002dword_002dmatch"></a>
<a name="index-up_002dcase_002dword_002dmatch"></a>
<a name="index-down_002dcase_002dword_002dmatch"></a>
<a name="index-select_002dword_002dstyle"></a>
<a name="index-match_002dword_002dcontext"></a>
<a name="index-match_002dwords_002dby_002dstyle"></a>
</dd>
<dt><tt>forward-word-match</tt>, <tt>backward-word-match</tt></dt>
<dt><tt>kill-word-match</tt>, <tt>backward-kill-word-match</tt></dt>
<dt><tt>transpose-words-match</tt>, <tt>capitalize-word-match</tt></dt>
<dt><tt>up-case-word-match</tt>, <tt>down-case-word-match</tt></dt>
<dt><tt>select-word-style</tt>, <tt>match-word-context</tt>, <tt>match-words-by-style</tt></dt>
<dd><p>The eight ‘<tt>-match</tt>’ functions are drop-in replacements for the
builtin widgets without the suffix. By default they behave in a similar
way. However, by the use of styles and the function <tt>select-word-style</tt>,
the way words are matched can be altered.
</p>
<p>The simplest way of configuring the functions is to use
<tt>select-word-style</tt>, which can either be called as a normal function with
the appropriate argument, or invoked as a user-defined widget that will
prompt for the first character of the word style to be used. The first
time it is invoked, the eight <tt>-match</tt> functions will automatically
replace the builtin versions, so they do not need to be loaded explicitly.
</p>
<p>The word styles available are as follows. Only the first character
is examined.
</p>
<dl compact="compact">
<dt><tt>bash</tt></dt>
<dd><p>Word characters are alphanumeric characters only.
</p>
</dd>
<dt><tt>normal</tt></dt>
<dd><p>As in normal shell operation: word characters are alphanumeric characters
plus any characters present in the string given by the parameter
<tt>$WORDCHARS</tt>.
</p>
</dd>
<dt><tt>shell</tt></dt>
<dd><p>Words are complete shell command arguments, possibly including complete
quoted strings, or any tokens special to the shell.
</p>
</dd>
<dt><tt>whitespace</tt></dt>
<dd><p>Words are any set of characters delimited by whitespace.
</p>
</dd>
<dt><tt>default</tt></dt>
<dd><p>Restore the default settings; this is usually the same as ‘<tt>normal</tt>’.
</p>
</dd>
</dl>
<p>All but ‘<tt>default</tt>’ can be input as an upper case character, which has
the same effect but with subword matching turned on. In this case, words
with upper case characters are treated specially: each separate run of
upper case characters, or an upper case character followed by any number of
other characters, is considered a word. The style <tt>subword-range</tt>
can supply an alternative character range to the default ‘<tt>[:upper:]</tt>’;
the value of the style is treated as the contents of a ‘<tt>[</tt><var>...</var><tt>]</tt>’
pattern (note that the outer brackets should not be supplied, only
those surrounding named ranges).
</p>
<p>More control can be obtained using the <tt>zstyle</tt> command, as described in
<a href="Zsh-Modules.html#The-zsh_002fzutil-Module">The zsh/zutil Module</a>. Each style is looked up in the
context <tt>:zle:</tt><var>widget</var> where <var>widget</var> is the name of the
user-defined widget, not the name of the function implementing it, so in
the case of the definitions supplied by <tt>select-word-style</tt> the
appropriate contexts are <tt>:zle:forward-word</tt>, and so on. The function
<tt>select-word-style</tt> itself always defines styles for the context
‘<tt>:zle:*</tt>’ which can be overridden by more specific (longer) patterns as
well as explicit contexts.
</p>
<p>The style <tt>word-style</tt> specifies the rules to use. This may have the
following values.
</p>
<dl compact="compact">
<dt><tt>normal</tt></dt>
<dd><p>Use the standard shell rules, i.e. alphanumerics and <tt>$WORDCHARS</tt>, unless
overridden by the styles <tt>word-chars</tt> or <tt>word-class</tt>.
</p>
</dd>
<dt><tt>specified</tt></dt>
<dd><p>Similar to <tt>normal</tt>, but <em>only</em> the specified characters, and not also
alphanumerics, are considered word characters.
</p>
</dd>
<dt><tt>unspecified</tt></dt>
<dd><p>The negation of specified. The given characters are those which will
<em>not</em> be considered part of a word.
</p>
</dd>
<dt><tt>shell</tt></dt>
<dd><p>Words are obtained by using the syntactic rules for generating shell
command arguments. In addition, special tokens which are never command
arguments such as ‘<tt>()</tt>’ are also treated as words.
</p>
</dd>
<dt><tt>whitespace</tt></dt>
<dd><p>Words are whitespace-delimited strings of characters.
</p>
</dd>
</dl>
<p>The first three of those rules usually use <tt>$WORDCHARS</tt>, but the value
in the parameter can be overridden by the style <tt>word-chars</tt>, which works
in exactly the same way as <tt>$WORDCHARS</tt>. In addition, the style
<tt>word-class</tt> uses character class syntax to group characters and takes
precedence over <tt>word-chars</tt> if both are set. The <tt>word-class</tt> style
does not include the surrounding brackets of the character class; for
example, ‘<tt>-:[:alnum:]</tt>’ is a valid <tt>word-class</tt> to include all
alphanumerics plus the characters ‘<tt>-</tt>’ and ‘<tt>:</tt>’. Be careful
including ‘<tt>]</tt>’, ‘<tt>^</tt>’ and ‘<tt>-</tt>’ as these are special inside
character classes.
</p>
<p><tt>word-style</tt> may also have ‘<tt>-subword</tt>’ appended to its value to
turn on subword matching, as described above.
</p>
<p>The style <tt>skip-chars</tt> is mostly useful for
<tt>transpose-words</tt> and similar functions. If set, it gives a count of
characters starting at the cursor position which will not be considered
part of the word and are treated as space, regardless of what they actually
are. For example, if
</p>
<div class="example">
<pre class="example">zstyle ':zle:transpose-words' skip-chars 1
</pre></div>
<p>has been set, and <tt>transpose-words-match</tt> is called with the cursor on
the <var>X</var> of <tt>foo</tt><var>X</var><tt>bar</tt>, where <var>X</var> can be any character, then
the resulting expression is <tt>bar</tt><var>X</var><tt>foo</tt>.
</p>
<p>Finer grained control can be obtained by setting the style <tt>word-context</tt>
to an array of pairs of entries. Each pair of entries consists of a
<var>pattern</var> and a <var>subcontext</var>. The shell argument the cursor is on is
matched against each <var>pattern</var> in turn until one matches; if it does,
the context is extended by a colon and the corresponding <var>subcontext</var>.
Note that the test is made against the original word on the line, with no
stripping of quotes. Special handling is done between words: the current
context is examined and if it contains the string <tt>back</tt>, the word before
the cursor is considered, else the word after cursor is considered. Some
examples are given below.
</p>
<p>The style <tt>skip-whitespace-first</tt> is only used with the
<tt>forward-word</tt> widget. If it is set to true, then <tt>forward-word</tt>
skips any non-word-characters, followed by any non-word-characters:
this is similar to the behaviour of other word-orientated widgets,
and also that used by other editors, however it differs from the
standard zsh behaviour. When using <tt>select-word-style</tt> the widget
is set in the context <tt>:zle:*</tt> to <tt>true</tt> if the word style is
<tt>bash</tt> and <tt>false</tt> otherwise. It may be overridden by setting it in
the more specific context <tt>:zle:forward-word*</tt>.
</p>
<p>Here are some examples of use of the styles, actually taken from the
simplified interface in <tt>select-word-style</tt>:
</p>
<div class="example">
<pre class="example">zstyle ':zle:*' word-style standard
zstyle ':zle:*' word-chars ''
</pre></div>
<p>Implements bash-style word handling for all widgets, i.e. only
alphanumerics are word characters; equivalent to setting
the parameter <tt>WORDCHARS</tt> empty for the given context.
</p>
<div class="example">
<pre class="example">style ':zle:*kill*' word-style space
</pre></div>
<p>Uses space-delimited words for widgets with the word ‘kill’ in the name.
Neither of the styles <tt>word-chars</tt> nor <tt>word-class</tt> is used in this case.
</p>
<p>Here are some examples of use of the <tt>word-context</tt> style to extend
the context.
</p>
<div class="example">
<pre class="example">zstyle ':zle:*' word-context \
"*/*" file "[[:space:]]" whitespace
zstyle ':zle:transpose-words:whitespace' word-style shell
zstyle ':zle:transpose-words:filename' word-style normal
zstyle ':zle:transpose-words:filename' word-chars ''
</pre></div>
<p>This provides two different ways of using <tt>transpose-words</tt> depending on
whether the cursor is on whitespace between words or on a filename, here
any word containing a <tt>/</tt>. On whitespace, complete arguments as defined
by standard shell rules will be transposed. In a filename, only
alphanumerics will be transposed. Elsewhere, words will be transposed
using the default style for <tt>:zle:transpose-words</tt>.
</p>
<p>The word matching and all the handling of <tt>zstyle</tt> settings is actually
implemented by the function <tt>match-words-by-style</tt>. This can be used to
create new user-defined widgets. The calling function should set the local
parameter <tt>curcontext</tt> to <tt>:zle:</tt><var>widget</var>, create the local
parameter <tt>matched_words</tt> and call <tt>match-words-by-style</tt> with no
arguments. On return, <tt>matched_words</tt> will be set to an array with the
elements: (1) the start of the line (2) the word before the cursor (3) any
non-word characters between that word and the cursor (4) any non-word
character at the cursor position plus any remaining non-word characters
before the next word, including all characters specified by the
<tt>skip-chars</tt> style, (5) the word at or following the cursor (6) any
non-word characters following that word (7) the remainder of the line. Any
of the elements may be an empty string; the calling function should test
for this to decide whether it can perform its function.
</p>
<p>It is possible to pass options with arguments to <tt>match-words-by-style</tt>
to override the use of styles. The options are:
</p><dl compact="compact">
<dt><tt>-w</tt></dt>
<dd><p><var>word-style</var>
</p></dd>
<dt><tt>-s</tt></dt>
<dd><p><var>skip-chars</var>
</p></dd>
<dt><tt>-c</tt></dt>
<dd><p><var>word-class</var>
</p></dd>
<dt><tt>-C</tt></dt>
<dd><p><var>word-chars</var>
</p></dd>
<dt><tt>-r</tt></dt>
<dd><p><var>subword-range</var>
</p></dd>
</dl>
<p>For example, <tt>match-words-by-style -w shell -c 0</tt> may be used to
extract the command argument around the cursor.
</p>
<p>The <tt>word-context</tt> style is implemented by the function
<tt>match-word-context</tt>. This should not usually need to be called
directly.
</p>
<a name="index-copy_002dearlier_002dword"></a>
</dd>
<dt><tt>copy-earlier-word</tt></dt>
<dd><p>This widget works like a combination of <tt>insert-last-word</tt> and
<tt>copy-prev-shell-word</tt>. Repeated invocations of the widget retrieve
earlier words on the relevant history line. With a numeric argument
<var>N</var>, insert the <var>N</var>th word from the history line; <var>N</var> may be
negative to count from the end of the line.
</p>
<p>If <tt>insert-last-word</tt> has been used to retrieve the last word on a
previous history line, repeated invocations will replace that word with
earlier words from the same line.
</p>
<p>Otherwise, the widget applies to words on the line currently being edited.
The <tt>widget</tt> style can be set to the name of another widget that should
be called to retrieve words. This widget must accept the same three
arguments as <tt>insert-last-word</tt>.
</p>
<a name="index-cycle_002dcompletion_002dpositions"></a>
</dd>
<dt><tt>cycle-completion-positions</tt></dt>
<dd><p>After inserting an unambiguous string into the command line, the new
function based completion system may know about multiple places in
this string where characters are missing or differ from at least one
of the possible matches. It will then place the cursor on the
position it considers to be the most interesting one, i.e. the one
where one can disambiguate between as many matches as possible with as
little typing as possible.
</p>
<p>This widget allows the cursor to be easily moved to the other interesting
spots. It can be invoked repeatedly to cycle between all positions
reported by the completion system.
</p>
<a name="index-delete_002dwhole_002dword_002dmatch"></a>
</dd>
<dt><tt>delete-whole-word-match</tt></dt>
<dd><p>This is another function which works like the <tt>-match</tt> functions
described immediately above, i.e. using styles to decide the word
boundaries. However, it is not a replacement for any existing function.
</p>
<p>The basic behaviour is to delete the word around the cursor. There is no
numeric argument handling; only the single word around the cursor is
considered. If the widget contains the string <tt>kill</tt>, the removed text
will be placed in the cutbuffer for future yanking. This can be obtained
by defining <tt>kill-whole-word-match</tt> as follows:
</p>
<div class="example">
<pre class="example">zle -N kill-whole-word-match delete-whole-word-match
</pre></div>
<p>and then binding the widget <tt>kill-whole-word-match</tt>.
</p>
<a name="index-down_002dline_002dor_002dbeginning_002dsearch"></a>
<a name="index-up_002dline_002dor_002dbeginning_002dsearch"></a>
</dd>
<dt><tt>up-line-or-beginning-search</tt>, <tt>down-line-or-beginning-search</tt></dt>
<dd><p>These widgets are similar to the builtin functions <tt>up-line-or-search</tt>
and <tt>down-line-or-search</tt>: if in a multiline buffer they move up or
down within the buffer, otherwise they search for a history line matching
the start of the current line. In this case, however, they search for
a line which matches the current line up to the current cursor position, in
the manner of <tt>history-beginning-search-backward</tt> and <tt>-forward</tt>, rather
than the first word on the line.
</p>
<a name="index-edit_002dcommand_002dline"></a>
</dd>
<dt><tt>edit-command-line</tt></dt>
<dd><p>Edit the command line using your visual editor, as in <tt>ksh</tt>.
</p>
<div class="example">
<pre class="example">bindkey -M vicmd v edit-command-line
</pre></div>
<a name="index-expand_002dabsolute_002dpath"></a>
</dd>
<dt><tt>expand-absolute-path</tt></dt>
<dd><p>Expand the file name under the cursor to an absolute path, resolving
symbolic links. Where possible, the initial path segment is turned
into a named directory or reference to a user’s home directory.
</p>
<a name="index-history_002dbeginning_002dsearch_002dbackward_002dend"></a>
<a name="index-history_002dbeginning_002dsearch_002dforward_002dend"></a>
</dd>
<dt><tt>history-search-end</tt></dt>
<dd><p>This function implements the widgets
<tt>history-beginning-search-backward-end</tt> and
<tt>history-beginning-search-forward-end</tt>. These commands work by first
calling the corresponding builtin widget (see
<a href="Zsh-Line-Editor.html#History-Control">History Control</a>) and then moving the cursor to the end of the line. The original cursor
position is remembered and restored before calling the builtin widget a
second time, so that the same search is repeated to look farther through
the history.
</p>
<p>Although you <tt>autoload</tt> only one function, the commands to use it are
slightly different because it implements two widgets.
</p>
<div class="example">
<pre class="example">zle -N history-beginning-search-backward-end \
history-search-end
zle -N history-beginning-search-forward-end \
history-search-end
bindkey '\e^P' history-beginning-search-backward-end
bindkey '\e^N' history-beginning-search-forward-end
</pre></div>
<a name="index-history_002dbeginning_002dsearch_002dmenu"></a>
</dd>
<dt><tt>history-beginning-search-menu</tt></dt>
<dd><p>This function implements yet another form of history searching. The
text before the cursor is used to select lines from the history,
as for <tt>history-beginning-search-backward</tt> except that all matches are
shown in a numbered menu. Typing the appropriate digits inserts the
full history line. Note that leading zeroes must be typed (they are only
shown when necessary for removing ambiguity). The entire history is
searched; there is no distinction between forwards and backwards.
</p>
<p>With a numeric argument, the search is not anchored to the start of
the line; the string typed by the use may appear anywhere in the line
in the history.
</p>
<p>If the widget name contains ‘<tt>-end</tt>’ the cursor is moved to the end of
the line inserted. If the widget name contains ‘<tt>-space</tt>’ any space
in the text typed is treated as a wildcard and can match anything (hence
a leading space is equivalent to giving a numeric argument). Both
forms can be combined, for example:
</p>
<div class="example">
<pre class="example">zle -N history-beginning-search-menu-space-end \
history-beginning-search-menu
</pre></div>
<a name="index-history_002dpattern_002dsearch"></a>
<a name="index-history_002dpattern_002dsearch_002dbackward"></a>
<a name="index-history_002dpattern_002dsearch_002dforward"></a>
</dd>
<dt><tt>history-pattern-search</tt></dt>
<dd><p>The function <tt>history-pattern-search</tt> implements widgets which prompt
for a pattern with which to search the history backwards or forwards. The
pattern is in the usual zsh format, however the first character may be
<tt>^</tt> to anchor the search to the start of the line, and the last character
may be <tt>$</tt> to anchor the search to the end of the line. If the
search was not anchored to the end of the line the cursor is positioned
just after the pattern found.
</p>
<p>The commands to create bindable widgets are similar to those in the
example immediately above:
</p>
<div class="example">
<pre class="example">autoload -U history-pattern-search
zle -N history-pattern-search-backward history-pattern-search
zle -N history-pattern-search-forward history-pattern-search
</pre></div>
<a name="index-incarg"></a>
<a name="index-incarg_002c-use-of"></a>
</dd>
<dt><tt>incarg</tt></dt>
<dd><p>Typing the keystrokes for this widget with the cursor placed on or to the
left of an integer causes that integer to be incremented by one. With a
numeric argument, the number is incremented by the amount of the
argument (decremented if the numeric argument is negative). The shell
parameter <tt>incarg</tt> may be set to change the default increment to
something other than one.
</p>
<div class="example">
<pre class="example">bindkey '^X+' incarg
</pre></div>
<a name="index-incremental_002dcomplete_002dword"></a>
</dd>
<dt><tt>incremental-complete-word</tt></dt>
<dd><p>This allows incremental completion of a word. After starting this
command, a list of completion choices can be shown after every character
you type, which you can delete with <tt>^H</tt> or <tt>DEL</tt>. Pressing return
accepts the completion so far and returns you to normal editing (that is,
the command line is <em>not</em> immediately executed). You can hit <tt>TAB</tt> to
do normal completion, <tt>^G</tt> to abort back to the state when you started,
and <tt>^D</tt> to list the matches.
</p>
<p>This works only with the new function based completion system.
</p>
<div class="example">
<pre class="example">bindkey '^Xi' incremental-complete-word
</pre></div>
<a name="index-insert_002dcomposed_002dchar"></a>
</dd>
<dt><tt>insert-composed-char</tt></dt>
<dd><p>This function allows you to compose characters that don’t appear on the
keyboard to be inserted into the command line. The command is followed by
two keys corresponding to ASCII characters (there is no prompt). For
accented characters, the two keys are a base character followed by a code
for the accent, while for other special characters the two characters
together form a mnemonic for the character to be inserted. The
two-character codes are a subset of those given by RFC 1345 (see for
example <tt><a href="http://www.faqs.org/rfcs/rfc1345.html">http://www.faqs.org/rfcs/rfc1345.html</a></tt>).
</p>
<p>The function may optionally be followed by up to two characters which
replace one or both of the characters read from the keyboard; if both
characters are supplied, no input is read. For example,
<tt>insert-composed-char a:</tt> can be used within a widget to insert an a with
umlaut into the command line. This has the advantages over use of a
literal character that it is more portable.
</p>
<p>For best results zsh should have been built with support for multibyte
characters (configured with <tt>--enable-multibyte</tt>); however, the function
works for the limited range of characters available in single-byte
character sets such as ISO-8859-1.
</p>
<p>The character is converted into the local representation and
inserted into the command line at the cursor position.
(The conversion is done within the shell, using whatever facilities
the C library provides.) With a numeric argument, the character and its
code are previewed in the status line
</p>
<p>The function may be run outside zle in which case it prints the character
(together with a newline) to standard output. Input is still read from
keystrokes.
</p>
<p>See <tt>insert-unicode-char</tt> for an alternative way of inserting Unicode
characters using their hexadecimal character number.
</p>
<p>The set of accented characters is reasonably complete up to Unicode
character U+0180, the set of special characters less so. However, it
is very sporadic from that point. Adding new characters is easy,
however; see the function <tt>define-composed-chars</tt>. Please send any
additions to <tt>zsh-workers@zsh.org</tt>.
</p>
<p>The codes for the second character when used to accent the first are as
follows. Note that not every character can take every accent.
</p><dl compact="compact">
<dt><tt>!</tt></dt>
<dd><p>Grave.
</p></dd>
<dt><tt>'</tt></dt>
<dd><p>Acute.
</p></dd>
<dt><tt>></tt></dt>
<dd><p>Circumflex.
</p></dd>
<dt><tt>?</tt></dt>
<dd><p>Tilde. (This is not <tt>~</tt> as RFC 1345 does not assume that
character is present on the keyboard.)
</p></dd>
<dt><tt>-</tt></dt>
<dd><p>Macron. (A horizontal bar over the base character.)
</p></dd>
<dt><tt>(</tt></dt>
<dd><p>Breve. (A shallow dish shape over the base character.)
</p></dd>
<dt><tt>.</tt></dt>
<dd><p>Dot above the base character, or in the case of <tt>i</tt> no dot,
or in the case of <tt>L</tt> and <tt>l</tt> a centered dot.
</p></dd>
<dt><tt>:</tt></dt>
<dd><p>Diaeresis (Umlaut).
</p></dd>
<dt><tt>c</tt></dt>
<dd><p>Cedilla.
</p></dd>
<dt><tt>_</tt></dt>
<dd><p>Underline, however there are currently no underlined characters.
</p></dd>
<dt><tt>/</tt></dt>
<dd><p>Stroke through the base character.
</p></dd>
<dt><tt>"</tt></dt>
<dd><p>Double acute (only supported on a few letters).
</p></dd>
<dt><tt>;</tt></dt>
<dd><p>Ogonek. (A little forward facing hook at the bottom right
of the character.)
</p></dd>
<dt><tt><</tt></dt>
<dd><p>Caron. (A little v over the letter.)
</p></dd>
<dt><tt>0</tt></dt>
<dd><p>Circle over the base character.
</p></dd>
<dt><tt>2</tt></dt>
<dd><p>Hook over the base character.
</p></dd>
<dt><tt>9</tt></dt>
<dd><p>Horn over the base character.
</p></dd>
</dl>
<p>The most common characters from the Arabic, Cyrillic, Greek and Hebrew
alphabets are available; consult RFC 1345 for the appropriate sequences.
In addition, a set of two letter codes not in RFC 1345 are available for
the double-width characters corresponding to ASCII characters from <tt>!</tt>
to <tt>~</tt> (0x21 to 0x7e) by preceding the character with <tt>^</tt>, for
example <tt>^A</tt> for a double-width <tt>A</tt>.
</p>
<p>The following other two-character sequences are understood.
</p>
<dl compact="compact">
<dt>ASCII characters</dt>
<dd><p>These are already present on most keyboards:
</p><dl compact="compact">
<dt><tt><(</tt></dt>
<dd><p>Left square bracket
</p></dd>
<dt><tt>//</tt></dt>
<dd><p>Backslash (solidus)
</p></dd>
<dt><tt>)></tt></dt>
<dd><p>Right square bracket
</p></dd>
<dt><tt>(!</tt></dt>
<dd><p>Left brace (curly bracket)
</p></dd>
<dt><tt>!!</tt></dt>
<dd><p>Vertical bar (pipe symbol)
</p></dd>
<dt><tt>!)</tt></dt>
<dd><p>Right brace (curly bracket)
</p></dd>
<dt><tt>'?</tt></dt>
<dd><p>Tilde
</p></dd>
</dl>
</dd>
<dt>Special letters</dt>
<dd><p>Characters found in various variants of the Latin alphabet:
</p><dl compact="compact">
<dt><tt>ss</tt></dt>
<dd><p>Eszett (scharfes S)
</p></dd>
<dt><tt>D-</tt>, <tt>d-</tt></dt>
<dd><p>Eth
</p></dd>
<dt><tt>TH</tt>, <tt>th</tt></dt>
<dd><p>Thorn
</p></dd>
<dt><tt>kk</tt></dt>
<dd><p>Kra
</p></dd>
<dt><tt>'n</tt></dt>
<dd><p>’n
</p></dd>
<dt><tt>NG</tt>, <tt>ng</tt></dt>
<dd><p>Ng
</p></dd>
<dt><tt>OI</tt>, <tt>oi</tt></dt>
<dd><p>Oi
</p></dd>
<dt><tt>yr</tt></dt>
<dd><p>yr
</p></dd>
<dt><tt>ED</tt></dt>
<dd><p>ezh
</p></dd>
</dl>
</dd>
<dt>Currency symbols</dt>
<dd><dl compact="compact">
<dt><tt>Ct</tt></dt>
<dd><p>Cent
</p></dd>
<dt><tt>Pd</tt></dt>
<dd><p>Pound sterling (also lira and others)
</p></dd>
<dt><tt>Cu</tt></dt>
<dd><p>Currency
</p></dd>
<dt><tt>Ye</tt></dt>
<dd><p>Yen
</p></dd>
<dt><tt>Eu</tt></dt>
<dd><p>Euro (N.B. not in RFC 1345)
</p></dd>
</dl>
</dd>
<dt>Punctuation characters</dt>
<dd><p>References to "right" quotes indicate the shape (like a 9 rather than 6)
rather than their grammatical use. (For example, a "right" low double
quote is used to open quotations in German.)
</p><dl compact="compact">
<dt><tt>!I</tt></dt>
<dd><p>Inverted exclamation mark
</p></dd>
<dt><tt>BB</tt></dt>
<dd><p>Broken vertical bar
</p></dd>
<dt><tt>SE</tt></dt>
<dd><p>Section
</p></dd>
<dt><tt>Co</tt></dt>
<dd><p>Copyright
</p></dd>
<dt><tt>-a</tt></dt>
<dd><p>Spanish feminine ordinal indicator
</p></dd>
<dt><tt><<</tt></dt>
<dd><p>Left guillemet
</p></dd>
<dt><tt>-</tt><tt>-</tt></dt>
<dd><p>Soft hyphen
</p></dd>
<dt><tt>Rg</tt></dt>
<dd><p>Registered trade mark
</p></dd>
<dt><tt>PI</tt></dt>
<dd><p>Pilcrow (paragraph)
</p></dd>
<dt><tt>-o</tt></dt>
<dd><p>Spanish masculine ordinal indicator
</p></dd>
<dt><tt>>></tt></dt>
<dd><p>Right guillemet
</p></dd>
<dt><tt>?I</tt></dt>
<dd><p>Inverted question mark
</p></dd>
<dt><tt>-1</tt></dt>
<dd><p>Hyphen
</p></dd>
<dt><tt>-N</tt></dt>
<dd><p>En dash
</p></dd>
<dt><tt>-M</tt></dt>
<dd><p>Em dash
</p></dd>
<dt><tt>-3</tt></dt>
<dd><p>Horizontal bar
</p></dd>
<dt><tt>:3</tt></dt>
<dd><p>Vertical ellipsis
</p></dd>
<dt><tt>.3</tt></dt>
<dd><p>Horizontal midline ellipsis
</p></dd>
<dt><tt>!2</tt></dt>
<dd><p>Double vertical line
</p></dd>
<dt><tt>=2</tt></dt>
<dd><p>Double low line
</p></dd>
<dt><tt>'6</tt></dt>
<dd><p>Left single quote
</p></dd>
<dt><tt>'9</tt></dt>
<dd><p>Right single quote
</p></dd>
<dt><tt>.9</tt></dt>
<dd><p>"Right" low quote
</p></dd>
<dt><tt>9'</tt></dt>
<dd><p>Reversed "right" quote
</p></dd>
<dt><tt>"6</tt></dt>
<dd><p>Left double quote
</p></dd>
<dt><tt>"9</tt></dt>
<dd><p>Right double quote
</p></dd>
<dt><tt>:9</tt></dt>
<dd><p>"Right" low double quote
</p></dd>
<dt><tt>9"</tt></dt>
<dd><p>Reversed "right" double quote
</p></dd>
<dt><tt>/-</tt></dt>
<dd><p>Dagger
</p></dd>
<dt><tt>/=</tt></dt>
<dd><p>Double dagger
</p></dd>
</dl>
</dd>
<dt>Mathematical symbols</dt>
<dd><dl compact="compact">
<dt><tt>DG</tt></dt>
<dd><p>Degree
</p></dd>
<dt><tt>-2</tt>, <tt>+-</tt>, <tt>-+</tt></dt>
<dd><p>- sign, +/- sign, -/+ sign
</p></dd>
<dt><tt>2S</tt></dt>
<dd><p>Superscript 2
</p></dd>
<dt><tt>3S</tt></dt>
<dd><p>Superscript 3
</p></dd>
<dt><tt>1S</tt></dt>
<dd><p>Superscript 1
</p></dd>
<dt><tt>My</tt></dt>
<dd><p>Micro
</p></dd>
<dt><tt>.M</tt></dt>
<dd><p>Middle dot
</p></dd>
<dt><tt>14</tt></dt>
<dd><p>Quarter
</p></dd>
<dt><tt>12</tt></dt>
<dd><p>Half
</p></dd>
<dt><tt>34</tt></dt>
<dd><p>Three quarters
</p></dd>
<dt><tt>*X</tt></dt>
<dd><p>Multiplication
</p></dd>
<dt><tt>-:</tt></dt>
<dd><p>Division
</p></dd>
<dt><tt>%0</tt></dt>
<dd><p>Per mille
</p></dd>
<dt><tt>FA</tt>, <tt>TE</tt>, <tt>/0</tt></dt>
<dd><p>For all, there exists, empty set
</p></dd>
<dt><tt>dP</tt>, <tt>DE</tt>, <tt>NB</tt></dt>
<dd><p>Partial derivative, delta (increment), del
(nabla)
</p></dd>
<dt><tt>(-</tt>, <tt>-)</tt></dt>
<dd><p>Element of, contains
</p></dd>
<dt><tt>*P</tt>, <tt>+Z</tt></dt>
<dd><p>Product, sum
</p></dd>
<dt><tt>*-</tt>, <tt>Ob</tt>, <tt>Sb</tt></dt>
<dd><p>Asterisk, ring, bullet
</p></dd>
<dt><tt>RT</tt>, <tt>0(</tt>, <tt>00</tt></dt>
<dd><p>Root sign, proportional to, infinity
</p></dd>
</dl>
</dd>
<dt>Other symbols</dt>
<dd><dl compact="compact">
<dt><tt>cS</tt>, <tt>cH</tt>, <tt>cD</tt>, <tt>cC</tt></dt>
<dd><p>Card suits: spades, hearts, diamonds,
clubs
</p></dd>
<dt><tt>Md</tt>, <tt>M8</tt>, <tt>M2</tt>, <tt>Mb</tt>, <tt>Mx</tt>, <tt>MX</tt></dt>
<dd><p>Musical notation:
crotchet (quarter note), quaver (eighth note), semiquavers (sixteenth
notes), flag sign, natural sign, sharp sign
</p></dd>
<dt><tt>Fm</tt>, <tt>Ml</tt></dt>
<dd><p>Female, male
</p></dd>
</dl>
</dd>
<dt>Accents on their own</dt>
<dd><dl compact="compact">
<dt><tt>'></tt></dt>
<dd><p>Circumflex (same as caret, <tt>^</tt>)
</p></dd>
<dt><tt>'!</tt></dt>
<dd><p>Grave (same as backtick, <tt>`</tt>)
</p></dd>
<dt><tt>',</tt></dt>
<dd><p>Cedilla
</p></dd>
<dt><tt>':</tt></dt>
<dd><p>Diaeresis (Umlaut)
</p></dd>
<dt><tt>'m</tt></dt>
<dd><p>Macron
</p></dd>
<dt><tt>''</tt></dt>
<dd><p>Acute
</p></dd>
</dl>
</dd>
</dl>
<a name="index-insert_002dfiles"></a>
</dd>
<dt><tt>insert-files</tt></dt>
<dd><p>This function allows you type a file pattern, and see the results of the
expansion at each step. When you hit return, all expansions are inserted
into the command line.
</p>
<div class="example">
<pre class="example">bindkey '^Xf' insert-files
</pre></div>
<a name="index-insert_002dunicode_002dchar"></a>
</dd>
<dt><tt>insert-unicode-char</tt></dt>
<dd><p>When first executed, the user inputs a set of hexadecimal digits.
This is terminated with another call to <tt>insert-unicode-char</tt>.
The digits are then turned into the corresponding Unicode character.
For example, if the widget is bound to <tt>^XU</tt>, the character sequence
‘<tt>^XU 4 c ^XU</tt>’ inserts <tt>L</tt> (Unicode U+004c).
</p>
<p>See <tt>insert-composed-char</tt> for a way of inserting characters
using a two-character mnemonic.
</p>
<a name="index-narrow_002dto_002dregion"></a>
<a name="index-narrow_002dto_002dregion_002dinvisible"></a>
</dd>
<dt><tt>narrow-to-region </tt>[ <tt>-p</tt> <var>pre</var> ] [ <tt>-P</tt> <var>post</var> ]</dt>
<dt><tt> </tt>[ <tt>-S</tt> <var>statepm</var> | <tt>-R</tt> <var>statepm</var> | [ <tt>-l</tt> <var>lbufvar</var> ] [ <tt>-r</tt> <var>rbufvar</var> ] ]</dt>
<dt><tt> </tt>[ <tt>-n</tt> ] [ <var>start</var> <var>end</var> ]</dt>
<dt><tt>narrow-to-region-invisible</tt></dt>
<dd><p>Narrow the editable portion of the buffer to the region between the cursor
and the mark, which may be in either order. The region may not be empty.
</p>
<p><tt>narrow-to-region</tt> may be used as a widget or called as a function from a
user-defined widget; by default, the text outside the editable area remains
visible. A <tt>recursive-edit</tt> is performed and the original widening
status is then restored. Various options and arguments are available when
it is called as a function.
</p>
<p>The options <tt>-p</tt> <var>pretext</var> and <tt>-P</tt> <var>posttext</var> may be
used to replace the text before and after the display for the duration of
the function; either or both may be an empty string.
</p>
<p>If the option <tt>-n</tt> is also given, <var>pretext</var> or <var>posttext</var> will only
be inserted if there is text before or after the region respectively which
will be made invisible.
</p>
<p>Two numeric arguments may be given which will be used instead of the cursor
and mark positions.
</p>
<p>The option <tt>-S</tt> <var>statepm</var> is used to narrow according to the other
options while saving the original state in the parameter with name
<var>statepm</var>, while the option <tt>-R</tt> <var>statepm</var> is used to restore the
state from the parameter; note in both cases the <em>name</em> of the parameter
is required. In the second case, other options and arguments are
irrelevant. When this method is used, no <tt>recursive-edit</tt> is performed;
the calling widget should call this function with the option <tt>-S</tt>,
perform its own editing on the command line or pass control to the user
via ‘<tt>zle recursive-edit</tt>’, then call this function with the option
<tt>-R</tt>. The argument <var>statepm</var> must be a suitable name for an ordinary
parameter, except that parameters beginning with the prefix <tt>_ntr_</tt> are
reserved for use within <tt>narrow-to-region</tt>. Typically the parameter will
be local to the calling function.
</p>
<p>The options <tt>-l</tt> <var>lbufvar</var> and <tt>-r</tt> <var>rbufvar</var> may be used to
specify parameters where the widget will store the resulting text from
the operation. The parameter <var>lbufvar</var> will contain <tt>LBUFFER</tt>
and <var>rbufvar</var> will contain <tt>RBUFFER</tt>. Neither of these two options
may be used with <tt>-S</tt> or <tt>-R</tt>.
</p>
<p><tt>narrow-to-region-invisible</tt> is a simple widget which calls
<tt>narrow-to-region</tt> with arguments which replace any text outside the
region with ‘<tt>...</tt>’. It does not take any arguments.
</p>
<p>The display is restored (and the widget returns) upon any zle command
which would usually cause the line to be accepted or aborted. Hence an
additional such command is required to accept or abort the current line.
</p>
<p>The return status of both widgets is zero if the line was accepted, else
non-zero.
</p>
<p>Here is a trivial example of a widget using this feature.
</p><div class="example">
<pre class="example">local state
narrow-to-region -p $'Editing restricted region\n' \
-P '' -S state
zle recursive-edit
narrow-to-region -R state
</pre></div>
<a name="index-predict_002don"></a>
<a name="index-predict_002doff"></a>
</dd>
<dt><tt>predict-on</tt></dt>
<dd><p>This set of functions implements predictive typing using history search.
After <tt>predict-on</tt>, typing characters causes the editor to look backward
in the history for the first line beginning with what you have typed so
far. After <tt>predict-off</tt>, editing returns to normal for the line found.
In fact, you often don’t even need to use <tt>predict-off</tt>, because if the
line doesn’t match something in the history, adding a key performs
standard completion, and then inserts itself if no completions were found.
However, editing in the middle of a line is liable to confuse prediction;
see the <tt>toggle</tt> style below.
</p>
<p>With the function based completion system (which is needed for this), you
should be able to type <tt>TAB</tt> at almost any point to advance the cursor
to the next ‘‘interesting’’ character position (usually the end of the
current word, but sometimes somewhere in the middle of the word). And of
course as soon as the entire line is what you want, you can accept with
return, without needing to move the cursor to the end first.
</p>
<p>The first time <tt>predict-on</tt> is used, it creates several additional
widget functions:
</p>
<dl compact="compact">
<dt><tt>delete-backward-and-predict</tt></dt>
<dd><p>Replaces the <tt>backward-delete-char</tt>
widget. You do not need to bind this yourself.
</p></dd>
<dt><tt>insert-and-predict</tt></dt>
<dd><p>Implements predictive typing by replacing the
<tt>self-insert</tt> widget. You do not need to bind this yourself.
</p></dd>
<dt><tt>predict-off</tt></dt>
<dd><p>Turns off predictive typing.
</p></dd>
</dl>
<p>Although you <tt>autoload</tt> only the <tt>predict-on</tt> function, it is
necessary to create a keybinding for <tt>predict-off</tt> as well.
</p>
<div class="example">
<pre class="example">zle -N predict-on
zle -N predict-off
bindkey '^X^Z' predict-on
bindkey '^Z' predict-off
</pre></div>
<a name="index-read_002dfrom_002dminibuffer"></a>
</dd>
<dt><tt>read-from-minibuffer</tt></dt>
<dd><p>This is most useful when called as a function from inside a widget, but will
work correctly as a widget in its own right. It prompts for a value
below the current command line; a value may be input using all of the
standard zle operations (and not merely the restricted set available
when executing, for example, <tt>execute-named-cmd</tt>). The value is then
returned to the calling function in the parameter <tt>$REPLY</tt> and the
editing buffer restored to its previous state. If the read was aborted
by a keyboard break (typically <tt>^G</tt>), the function returns status 1
and <tt>$REPLY</tt> is not set.
</p>
<p>If one argument is supplied to the function it is taken as a prompt,
otherwise ‘<tt>? </tt>’ is used. If two arguments are supplied, they are the
prompt and the initial value of <tt>$LBUFFER</tt>, and if a third argument is
given it is the initial value of <tt>$RBUFFER</tt>. This provides a default
value and starting cursor placement. Upon return the entire buffer is the
value of <tt>$REPLY</tt>.
</p>
<p>One option is available: ‘<tt>-k</tt> <var>num</var>’ specifies that <var>num</var>
characters are to be read instead of a whole line. The line editor is not
invoked recursively in this case, so depending on the terminal settings
the input may not be visible, and only the input keys are placed in
<tt>$REPLY</tt>, not the entire buffer. Note that unlike the <tt>read</tt> builtin
<var>num</var> must be given; there is no default.
</p>
<p>The name is a slight misnomer, as in fact the shell’s own minibuffer is
not used. Hence it is still possible to call <tt>executed-named-cmd</tt> and
similar functions while reading a value.
</p>
<a name="index-replace_002dargument"></a>
<a name="index-replace_002dargument_002dedit"></a>
</dd>
<dt><tt>replace-argument</tt>, <tt>replace-argument-edit</tt></dt>
<dd><p>The function <tt>replace-argument</tt> can be used to replace a command
line argument in the current command line or, if the current command
line is empty, in the last command line executed (the new command line
is not executed). Arguments are as delimited by standard shell syntax,
</p>
<p>If a numeric argument is given, that specifies the argument to be
replaced. 0 means the command name, as in history expansion.
A negative numeric argument counts backward from the last word.
</p>
<p>If no numeric argument is given, the current argument is replaced;
this is the last argument if the previous history line is being used.
</p>
<p>The function prompts for a replacement argument.
</p>
<p>If the widget contains the string <tt>edit</tt>, for example is defined as
</p>
<div class="example">
<pre class="example">zle -N replace-argument-edit replace-argument
</pre></div>
<p>then the function presents the current value of the argument for
editing, otherwise the editing buffer for the replacement is
initially empty.
</p>
<a name="index-replace_002dstring"></a>
<a name="index-replace_002dstring_002dagain"></a>
<a name="index-replace_002dpattern"></a>
</dd>
<dt><tt>replace-string</tt>, <tt>replace-pattern</tt></dt>
<dt><tt>replace-string-again</tt>, <tt>replace-pattern-again</tt></dt>
<dd><p>The function <tt>replace-string</tt> implements three widgets.
If defined under the same name as the function, it prompts for two
strings; the first (source) string will be replaced by the second
everywhere it occurs in the line editing buffer.
</p>
<p>If the widget name contains the word ‘<tt>pattern</tt>’, for example by
defining the widget using the command ‘<tt>zle -N replace-pattern
replace-string</tt>’, then the matching is performed using zsh patterns. All
zsh extended globbing patterns can be used in the source string; note
that unlike filename generation the pattern does not need to match an
entire word, nor do glob qualifiers have any effect. In addition, the
replacement string can contain parameter or command substitutions.
Furthermore, a ‘<tt>&</tt>’ in the replacement string will be replaced with
the matched source string, and a backquoted digit ‘<tt>\</tt><var>N</var>’ will be
replaced by the <var>N</var>th parenthesised expression matched. The form
‘<tt>\{</tt><var>N</var><tt>}</tt>’ may be used to protect the digit from following
digits.
</p>
<p>If the widget instead contains the word ‘<tt>regex</tt>’ (or ‘<tt>regexp</tt>’),
then the matching is performed using regular expressions, respecting
the setting of the option <tt>RE_MATCH_PCRE</tt> (see the description of the
function <tt>regexp-replace</tt> below). The special replacement facilities
described above for pattern matching are available.
</p>
<p>By default the previous source or replacement string will not be offered
for editing. However, this feature can be activated by setting the style
<tt>edit-previous</tt> in the context <tt>:zle:</tt><var>widget</var> (for example,
<tt>:zle:replace-string</tt>) to <tt>true</tt>. In addition, a positive
numeric argument forces the previous values to be offered, a negative or
zero argument forces them not to be.
</p>
<p>The function <tt>replace-string-again</tt> can be used to repeat the previous
replacement; no prompting is done. As with <tt>replace-string</tt>, if the name
of the widget contains the word ‘<tt>pattern</tt>’ or ‘<tt>regex</tt>’, pattern or
regular expression matching is performed, else a literal string
replacement. Note that the previous source and replacement text are the
same whether pattern, regular expression or string matching is used.
</p>
<p>In addition, <tt>replace-string</tt> shows the previous replacement above
the prompt, so long as there was one during the current session; if the
source string is empty, that replacement will be repeated without
the widget prompting for a replacement string.
</p>
<p>For example, starting from the line:
</p>
<div class="example">
<pre class="example">print This line contains fan and fond
</pre></div>
<p>and invoking <tt>replace-pattern</tt> with the source string
‘<tt>f(?)n</tt>’ and
the replacement string ‘<tt>c\1r</tt>’ produces the not very useful line:
</p>
<div class="example">
<pre class="example">print This line contains car and cord
</pre></div>
<p>The range of the replacement string can be limited by using the
<tt>narrow-to-region-invisible</tt> widget. One limitation of the current
version is that <tt>undo</tt> will cycle through changes to the replacement
and source strings before undoing the replacement itself.
</p>
<a name="index-send_002dinvisible"></a>
</dd>
<dt><tt>send-invisible</tt></dt>
<dd><p>This is similar to read-from-minibuffer in that it may be called as a
function from a widget or as a widget of its own, and interactively reads
input from the keyboard. However, the input being typed is concealed and
a string of asterisks (‘<tt>*</tt>’) is shown instead. The value is saved in
the parameter <tt>$INVISIBLE</tt> to which a reference is inserted into the
editing buffer at the restored cursor position. If the read was aborted
by a keyboard break (typically <tt>^G</tt>) or another escape from editing such
as <tt>push-line</tt>, <tt>$INVISIBLE</tt> is set to empty and the original buffer
is restored unchanged.
</p>
<p>If one argument is supplied to the function it is taken as a prompt,
otherwise ‘<tt>Non-echoed text: </tt>’ is used (as in emacs). If a second and
third argument are supplied they are used to begin and end the reference
to <tt>$INVISIBLE</tt> that is inserted into the buffer. The default is to
open with <tt>${</tt>, then <tt>INVISIBLE</tt>, and close with <tt>}</tt>, but many
other effects are possible.
</p>
<a name="index-smart_002dinsert_002dlast_002dword"></a>
</dd>
<dt><tt>smart-insert-last-word</tt></dt>
<dd><p>This function may replace the <tt>insert-last-word</tt> widget, like so:
</p>
<div class="example">
<pre class="example">zle -N insert-last-word smart-insert-last-word
</pre></div>
<p>With a numeric argument, or when passed command line arguments in a call
from another widget, it behaves like <tt>insert-last-word</tt>, except that
words in comments are ignored when <tt>INTERACTIVE_COMMENTS</tt> is set.
</p>
<p>Otherwise, the rightmost ‘‘interesting’’ word from the previous command is
found and inserted. The default definition of ‘‘interesting’’ is that the
word contains at least one alphabetic character, slash, or backslash.
This definition may be overridden by use of the <tt>match</tt> style. The
context used to look up the style is the widget name, so usually the
context is <tt>:insert-last-word</tt>. However, you can bind this function to
different widgets to use different patterns:
</p>
<div class="example">
<pre class="example">zle -N insert-last-assignment smart-insert-last-word
zstyle :insert-last-assignment match '[[:alpha:]][][[:alnum:]]#=*'
bindkey '\e=' insert-last-assignment
</pre></div>
<p>If no interesting word is found and the <tt>auto-previous</tt> style is set to
a true value, the search continues upward through the history. When
<tt>auto-previous</tt> is unset or false (the default), the widget must be
invoked repeatedly in order to search earlier history lines.
</p>
<a name="index-transpose_002dlines"></a>
</dd>
<dt><tt>transpose-lines</tt></dt>
<dd><p>Only useful with a multi-line editing buffer; the lines here are
lines within the current on-screen buffer, not history lines.
The effect is similar to the function of the same name in Emacs.
</p>
<p>Transpose the current line with the previous line and move the cursor
to the start of the next line. Repeating this (which can be done by
providing a positive numeric argument) has the effect of moving
the line above the cursor down by a number of lines.
</p>
<p>With a negative numeric argument, requires two lines above the
cursor. These two lines are transposed and the cursor moved to the
start of the previous line. Using a numeric argument less than -1
has the effect of moving the line above the cursor up by minus that
number of lines.
</p>
<a name="index-which_002dcommand-1"></a>
</dd>
<dt><tt>which-command</tt></dt>
<dd><p>This function is a drop-in replacement for the builtin widget
<tt>which-command</tt>. It has enhanced behaviour, in that it correctly
detects whether or not the command word needs to be expanded as an
alias; if so, it continues tracing the command word from the expanded
alias until it reaches the command that will be executed.
</p>
<p>The style <tt>whence</tt> is available in the context <tt>:zle:$WIDGET</tt>; this
may be set to an array to give the command and options that will be used to
investigate the command word found. The default is <tt>whence -c</tt>.
</p>
<a name="index-zcalc_002dauto_002dinsert"></a>
</dd>
<dt><tt>zcalc-auto-insert</tt></dt>
<dd><p>This function is useful together with the <tt>zcalc</tt> function described in
<a href="#Mathematical-Functions">Mathematical Functions</a>.
It should be bound to a key representing a binary operator such
as ‘<tt>+</tt>’, ‘<tt>-</tt>’, ‘<tt>*</tt>’ or ‘<tt>/</tt>’. When running in zcalc,
if the key occurs at the start of the line or immediately following
an open parenthesis, the text <tt>"ans "</tt> is inserted before the
representation of the key itself. This allows easy use of the
answer from the previous calculation in the current line. The
text to be inserted before the symbol typed can be modified by setting
the variable <tt>ZCALC_AUTO_INSERT_PREFIX</tt>.
</p>
<p>Hence, for example, typing ‘<tt>+12</tt>’ followed by return adds 12
to the previous result.
</p>
<p>When not in zcalc, the key simply inserts the symbol itself.
</p>
</dd>
</dl>
<hr>
<a name="Utility-Functions-1"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Widgets-1" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#ZLE-Functions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Styles-1" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.6.2 Utility Functions</h3>
<p>These functions are useful in constructing widgets. They
should be loaded with ‘<tt>autoload -U</tt> <var>function</var>’ and called
as indicated from user-defined widgets.
</p>
<dl compact="compact">
<dd><a name="index-split_002dshell_002darguments"></a>
</dd>
<dt><tt>split-shell-arguments</tt></dt>
<dd><p>This function splits the line currently being edited into shell arguments
and whitespace. The result is stored in the array <tt>reply</tt>. The array
contains all the parts of the line in order, starting with any whitespace
before the first argument, and finishing with any whitespace after the last
argument. Hence (so long as the option <tt>KSH_ARRAYS</tt> is not set)
whitespace is given by odd indices in the array and arguments by
even indices. Note that no stripping of quotes is done; joining together
all the elements of <tt>reply</tt> in order is guaranteed to produce the
original line.
</p>
<p>The parameter <tt>REPLY</tt> is set to the index of the word in <tt>reply</tt> which
contains the character after the cursor, where the first element has index
1. The parameter <tt>REPLY2</tt> is set to the index of the character under the
cursor in that word, where the first character has index 1.
</p>
<p>Hence <tt>reply</tt>, <tt>REPLY</tt> and <tt>REPLY2</tt> should all be made local to
the enclosing function.
</p>
<p>See the function <tt>modify-current-argument</tt>, described below, for
an example of how to call this function.
</p>
<a name="index-modify_002dcurrent_002dargument"></a>
</dd>
<dt><tt>modify-current-argument</tt> [ <var>expr-using-</var><tt>$ARG</tt> | <var>func</var> ]</dt>
<dd><p>This function provides a simple method of allowing user-defined widgets
to modify the command line argument under the cursor (or immediately to the
left of the cursor if the cursor is between arguments).
</p>
<p>The argument can be an expression which when evaluated operates on the shell
parameter <tt>ARG</tt>, which will have been set to the command line argument
under the cursor. The expression should be suitably quoted to prevent
it being evaluated too early.
</p>
<p>Alternatively, if the argument does not contain the string <tt>ARG</tt>, it
is assumed to be a shell function, to which the current command line
argument is passed as the only argument. The function should set the
variable <tt>REPLY</tt> to the new value for the command line argument.
If the function returns non-zero status, so does the calling function.
</p>
<p>For example, a user-defined widget containing the following code
converts the characters in the argument under the cursor into all upper
case:
</p>
<div class="example">
<pre class="example">modify-current-argument '${(U)ARG}'
</pre></div>
<p>The following strips any quoting from the current word (whether backslashes
or one of the styles of quotes), and replaces it with single quoting
throughout:
</p>
<div class="example">
<pre class="example">modify-current-argument '${(qq)${(Q)ARG}}'
</pre></div>
<p>The following performs directory expansion on the command line
argument and replaces it by the absolute path:
</p>
<div class="example">
<pre class="example">expand-dir() {
REPLY=${~1}
REPLY=${REPLY:a}
}
modify-current-argument expand-dir
</pre></div>
<p>In practice the function <tt>expand-dir</tt> would probably not be defined
within the widget where <tt>modify-current-argument</tt> is called.
</p>
</dd>
</dl>
<hr>
<a name="Styles-1"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Utility-Functions-1" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#ZLE-Functions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Exception-Handling" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.6.3 Styles</h3>
<p>The behavior of several of the above widgets can be controlled by the use
of the <tt>zstyle</tt> mechanism. In particular, widgets that interact with
the completion system pass along their context to any completions that
they invoke.
</p>
<dl compact="compact">
<dd><a name="index-break_002dkeys_002c-widget-style"></a>
</dd>
<dt><tt>break-keys</tt></dt>
<dd><p>This style is used by the <tt>incremental-complete-word</tt> widget. Its value
should be a pattern, and all keys matching this pattern will cause the
widget to stop incremental completion without the key having any further
effect. Like all styles used directly by
<tt>incremental-complete-word</tt>, this style is looked up using the
context ‘<tt>:incremental</tt>’.
</p>
<a name="index-completer_002c-completion-style-1"></a>
</dd>
<dt><tt>completer</tt></dt>
<dd><p>The <tt>incremental-complete-word</tt> and <tt>insert-and-predict</tt> widgets set
up their top-level context name before calling completion. This allows
one to define different sets of completer functions for normal completion
and for these widgets. For example, to use completion, approximation and
correction for normal completion, completion and correction for
incremental completion and only completion for prediction one could use:
</p>
<div class="example">
<pre class="example">zstyle ':completion:*' completer \
_complete _correct _approximate
zstyle ':completion:incremental:*' completer \
_complete _correct
zstyle ':completion:predict:*' completer \
_complete
</pre></div>
<p>It is a good idea to restrict the completers used in prediction, because
they may be automatically invoked as you type. The <tt>_list</tt> and
<tt>_menu</tt> completers should never be used with prediction. The
<tt>_approximate</tt>, <tt>_correct</tt>, <tt>_expand</tt>, and <tt>_match</tt> completers may
be used, but be aware that they may change characters anywhere in the word
behind the cursor, so you need to watch carefully that the result is what
you intended.
</p>
<a name="index-cursor_002c-completion-style"></a>
</dd>
<dt><tt>cursor</tt></dt>
<dd><p>The <tt>insert-and-predict</tt> widget uses this style, in the context
‘<tt>:predict</tt>’, to decide where to place the cursor after completion has
been tried. Values are:
</p>
<dl compact="compact">
<dt><tt>complete</tt></dt>
<dd><p>The cursor is left where it was when completion finished, but only if
it is after a character equal to the one just inserted by the user. If
it is after another character, this value is the same as ‘<tt>key</tt>’.
</p>
</dd>
<dt><tt>key</tt></dt>
<dd><p>The cursor is left
after the <var>n</var>th occurrence of the character just inserted, where
<var>n</var> is the number of times that character appeared in the word
before completion was attempted. In short, this has the effect of
leaving the cursor after the character just typed even if the
completion code found out that no other characters need to be inserted
at that position.
</p>
</dd>
</dl>
<p>Any other value for this style unconditionally leaves the cursor at the
position where the completion code left it.
</p>
<a name="index-list_002c-widget-style"></a>
</dd>
<dt><tt>list</tt></dt>
<dd><p>When using the <tt>incremental-complete-word</tt> widget, this style says
if the matches should be listed on every key press (if they fit on the
screen). Use the context prefix ‘<tt>:completion:incremental</tt>’.
</p>
<p>The <tt>insert-and-predict</tt> widget uses this style to decide if the
completion should be shown even if there is only one possible completion.
This is done if the value of this style is the string <tt>always</tt>. In this
case the context is ‘<tt>:predict</tt>’ (<em>not</em> ‘<tt>:completion:predict</tt>’).
</p>
<a name="index-match_002c-widget-style"></a>
</dd>
<dt><tt>match</tt></dt>
<dd><p>This style is used by <tt>smart-insert-last-word</tt> to provide a pattern
(using full <tt>EXTENDED_GLOB</tt> syntax) that matches an interesting word.
The context is the name of the widget to which <tt>smart-insert-last-word</tt>
is bound (see above). The default behavior of <tt>smart-insert-last-word</tt>
is equivalent to:
</p>
<div class="example">
<pre class="example">zstyle :insert-last-word match '*[[:alpha:]/\\]*'
</pre></div>
<p>However, you might want to include words that contain spaces:
</p>
<div class="example">
<pre class="example">zstyle :insert-last-word match '*[[:alpha:][:space:]/\\]*'
</pre></div>
<p>Or include numbers as long as the word is at least two characters long:
</p>
<div class="example">
<pre class="example">zstyle :insert-last-word match '*([[:digit:]]?|[[:alpha:]/\\])*'
</pre></div>
<p>The above example causes redirections like "2>" to be included.
</p>
<a name="index-prompt_002c-widget-style"></a>
</dd>
<dt><tt>prompt</tt></dt>
<dd><p>The <tt>incremental-complete-word</tt> widget shows the value of this
style in the status line during incremental completion. The string
value may contain any of the following substrings in the manner of
the <tt>PS1</tt> and other prompt parameters:
</p>
<dl compact="compact">
<dt><tt>%c</tt></dt>
<dd><p>Replaced by the name of the completer function that generated the
matches (without the leading underscore).
</p>
</dd>
<dt><tt>%l</tt></dt>
<dd><p>When the <tt>list</tt> style is set,
replaced by ‘<tt>...</tt>’ if the list of matches is too long to fit on the
screen and with an empty string otherwise. If the <tt>list</tt> style is
‘false’ or not set, ‘<tt>%l</tt>’ is always removed.
</p>
</dd>
<dt><tt>%n</tt></dt>
<dd><p>Replaced by the number of matches generated.
</p>
</dd>
<dt><tt>%s</tt></dt>
<dd><p>Replaced by ‘<tt>-no match-</tt>’, ‘<tt>-no prefix-</tt>’, or an empty string
if there is no completion matching the word on the line, if the
matches have no common prefix different from the word on the line, or
if there is such a common prefix, respectively.
</p>
</dd>
<dt><tt>%u</tt></dt>
<dd><p>Replaced by the unambiguous part of all matches, if there
is any, and if it is different from the word on the line.
</p>
</dd>
</dl>
<p>Like ‘<tt>break-keys</tt>’, this uses the ‘<tt>:incremental</tt>’ context.
</p>
<a name="index-stop_002dkeys_002c-widget-style"></a>
</dd>
<dt><tt>stop-keys</tt></dt>
<dd><p>This style is used by the <tt>incremental-complete-word</tt> widget. Its value
is treated similarly to the one for the <tt>break-keys</tt> style (and uses
the same context: ‘<tt>:incremental</tt>’). However, in
this case all keys matching the pattern given as its value will stop
incremental completion and will then execute their usual function.
</p>
<a name="index-toggle_002c-widget-style"></a>
</dd>
<dt><tt>toggle</tt></dt>
<dd><p>This boolean style is used by <tt>predict-on</tt> and its related widgets in
the context ‘<tt>:predict</tt>’. If set to one of the standard ‘true’ values,
predictive typing is automatically toggled off in situations where it is
unlikely to be useful, such as when editing a multi-line buffer or after
moving into the middle of a line and then deleting a character. The
default is to leave prediction turned on until an explicit call to
<tt>predict-off</tt>.
</p>
<a name="index-verbose_002c-widget-style"></a>
</dd>
<dt><tt>verbose</tt></dt>
<dd><p>This boolean style is used by <tt>predict-on</tt> and its related widgets in
the context ‘<tt>:predict</tt>’. If set to one of the standard ‘true’ values,
these widgets display a message below the prompt when the predictive state
is toggled. This is most useful in combination with the <tt>toggle</tt> style.
The default does not display these messages.
</p>
<a name="index-widget_002c-widget-style"></a>
</dd>
<dt><tt>widget</tt></dt>
<dd><p>This style is similar to the <tt>command</tt> style: For widget functions that
use <tt>zle</tt> to call other widgets, this style can sometimes be used to
override the widget which is called. The context for this style is the
name of the calling widget (<em>not</em> the name of the calling function,
because one function may be bound to multiple widget names).
</p>
<div class="example">
<pre class="example">zstyle :copy-earlier-word widget smart-insert-last-word
</pre></div>
<p>Check the documentation for the calling widget or function to determine
whether the <tt>widget</tt> style is used.
</p>
</dd>
</dl>
<hr>
<a name="Exception-Handling"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Styles-1" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#MIME-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Exception-Handling-1"></a>
<h2 class="section">26.7 Exception Handling</h2>
<p>Two functions are provided to enable zsh to provide exception handling in a
form that should be familiar from other languages.
</p>
<dl compact="compact">
<dd><a name="index-throw"></a>
</dd>
<dt><tt>throw</tt> <var>exception</var></dt>
<dd><p>The function <tt>throw</tt> throws the named <var>exception</var>. The name is
an arbitrary string and is only used by the <tt>throw</tt> and <tt>catch</tt>
functions. An exception is for the most part treated the same as a
shell error, i.e. an unhandled exception will cause the shell to abort all
processing in a function or script and to return to the top level in an
interactive shell.
</p>
</dd>
<dt><tt>catch</tt> <var>exception-pattern</var></dt>
<dd><p>The function <tt>catch</tt> returns status zero if an exception was thrown and
the pattern <var>exception-pattern</var> matches its name. Otherwise it
returns status 1. <var>exception-pattern</var> is a standard
shell pattern, respecting the current setting of the <tt>EXTENDED_GLOB</tt>
option. An alias <tt>catch</tt> is also defined to prevent the argument to the
function from matching filenames, so patterns may be used unquoted. Note
that as exceptions are not fundamentally different from other shell errors
it is possible to catch shell errors by using an empty string as the
exception name. The shell variable <tt>CAUGHT</tt> is set by <tt>catch</tt> to the
name of the exception caught. It is possible to rethrow an exception by
calling the <tt>throw</tt> function again once an exception has been caught.
<a name="index-catch"></a>
</p>
</dd>
</dl>
<p>The functions are designed to be used together with the <tt>always</tt> construct
described in
<a href="Shell-Grammar.html#Complex-Commands">Complex Commands</a>. This is important as only this
construct provides the required support for exceptions. A typical example
is as follows.
</p>
<div class="example">
<pre class="example">{
# "try" block
# ... nested code here calls "throw MyExcept"
} always {
# "always" block
if catch MyExcept; then
print "Caught exception MyExcept"
elif catch ''; then
print "Caught a shell error. Propagating..."
throw ''
fi
# Other exceptions are not handled but may be caught further
# up the call stack.
}
</pre></div>
<p>If all exceptions should be caught, the following idiom might be
preferable.
</p>
<div class="example">
<pre class="example">{
# ... nested code here throws an exception
} always {
if catch *; then
case $CAUGHT in
(MyExcept)
print "Caught my own exception"
;;
(*)
print "Caught some other exception"
;;
esac
fi
}
</pre></div>
<p>In common with exception handling in other languages, the exception may be
thrown by code deeply nested inside the ‘try’ block. However, note that it
must be thrown inside the current shell, not in a subshell forked for a
pipeline, parenthesised current-shell construct, or some form of
command or process substitution.
</p>
<p>The system internally uses the shell variable <tt>EXCEPTION</tt> to record the
name of the exception between throwing and catching. One drawback of this
scheme is that if the exception is not handled the variable <tt>EXCEPTION</tt>
remains set and may be incorrectly recognised as the name of an exception
if a shell error subsequently occurs. Adding <tt>unset EXCEPTION</tt> at the
start of the outermost layer of any code that uses exception handling will
eliminate this problem.
</p>
<hr>
<a name="MIME-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Exception-Handling" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Mathematical-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="MIME-Functions-1"></a>
<h2 class="section">26.8 MIME Functions</h2>
<p>Three functions are available to provide handling of files recognised by
extension, for example to dispatch a file <tt>text.ps</tt> when executed as a
command to an appropriate viewer.
</p>
<dl compact="compact">
<dd><a name="index-zsh_002dmime_002dsetup"></a>
<a name="index-zsh_002dmime_002dhandler"></a>
</dd>
<dt><tt>zsh-mime-setup</tt> [ <tt>-fv</tt> ] [ <tt>-l</tt> [ <var>suffix</var> ... ] ]</dt>
<dt><tt>zsh-mime-handler</tt> [ <tt>-l</tt> ] <var>command argument</var> ...</dt>
<dd><p>These two functions use the files <tt>~/.mime.types</tt> and <tt>/etc/mime.types</tt>,
which associate types and extensions, as well as <tt>~/.mailcap</tt> and
<tt>/etc/mailcap</tt> files, which associate types and the programs that
handle them. These are provided on many systems with the Multimedia
Internet Mail Extensions.
</p>
<p>To enable the system, the function <tt>zsh-mime-setup</tt> should be
autoloaded and run. This allows files with extensions to be treated
as executable; such files be completed by the function completion system.
The function <tt>zsh-mime-handler</tt> should not need to be called by the
user.
</p>
<p>The system works by setting up suffix aliases with ‘<tt>alias -s</tt>’.
Suffix aliases already installed by the user will not be overwritten.
</p>
<p>For suffixes defined in lower case, upper case variants will also
automatically be handled (e.g. <tt>PDF</tt> is automatically handled if
handling for the suffix <tt>pdf</tt> is defined), but not vice versa.
</p>
<p>Repeated calls to <tt>zsh-mime-setup</tt> do not override the existing
mapping between suffixes and executable files unless the option <tt>-f</tt>
is given. Note, however, that this does not override existing suffix
aliases assigned to handlers other than <tt>zsh-mime-handler</tt>.
</p>
<p>Calling <tt>zsh-mime-setup</tt> with the option <tt>-l</tt> lists the existing
mappings without altering them. Suffixes to list (which may contain
pattern characters that should be quoted from immediate interpretation
on the command line) may be given as additional arguments, otherwise
all suffixes are listed.
</p>
<p>Calling <tt>zsh-mime-setup</tt> with the option
<tt>-v</tt> causes verbose output to be shown during the setup operation.
</p>
<p>The system respects the <tt>mailcap</tt> flags <tt>needsterminal</tt> and
<tt>copiousoutput</tt>, see man page mailcap(4).
</p>
<p>The functions use the following styles, which are defined with the
<tt>zstyle</tt> builtin command (<a href="Zsh-Modules.html#The-zsh_002fzutil-Module">The zsh/zutil Module</a>). They should be defined
before <tt>zsh-mime-setup</tt> is run. The contexts used all
start with <tt>:mime:</tt>, with additional components in some cases.
It is recommended that a trailing <tt>*</tt> (suitably quoted) be appended
to style patterns in case the system is extended in future. Some
examples are given below.
</p>
<p>For files that have multiple suffixes, e.g. <tt>.pdf.gz</tt>, where the
context includes the suffix it will be looked up starting with the
longest possible suffix until a match for the style is found.
For example, if <tt>.pdf.gz</tt> produces a match for the handler, that
will be used; otherwise the handler for <tt>.gz</tt> will be used. Note
that, owing to the way suffix aliases work, it is always required that
there be a handler for the shortest possible suffix, so in this example
<tt>.pdf.gz</tt> can only be handled if <tt>.gz</tt> is also handled (though
not necessarily in the same way). Alternatively, if no handling
for <tt>.gz</tt> on its own is needed, simply adding the command
</p>
<div class="example">
<pre class="example">alias -s gz=zsh-mime-handler
</pre></div>
<p>to the initialisation code is sufficient; <tt>.gz</tt> will not be handled
on its own, but may be in combination with other suffixes.
</p>
<dl compact="compact">
<dd><a name="index-current_002dshell_002c-MIME-style"></a>
</dd>
<dt><tt>current-shell</tt></dt>
<dd><p>If this boolean style is true, the mailcap handler for the context in
question is run using the <tt>eval</tt> builtin instead of by starting a new
<tt>sh</tt> process. This is more efficient, but may not work in the occasional
cases where the mailcap handler uses strict POSIX syntax.
</p>
<a name="index-disown_002c-MIME-style"></a>
</dd>
<dt><tt>disown</tt></dt>
<dd><p>If this boolean style is true, mailcap handlers started in the
background will be disowned, i.e. not subject to job control within
the parent shell. Such handlers nearly always produce their own
windows, so the only likely harmful side effect of setting the style is
that it becomes harder to kill jobs from within the shell.
</p>
<a name="index-execute_002das_002dis_002c-MIME-style"></a>
</dd>
<dt><tt>execute-as-is</tt></dt>
<dd><p>This style gives a list of patterns to be matched against files
passed for execution with a handler program. If the file matches
the pattern, the entire command line is executed in its current form,
with no handler. This is useful for files which might have suffixes
but nonetheless be executable in their own right. If the style
is not set, the pattern <tt>*(*) *(/)</tt> is used;
hence executable files are executed directly and not passed to a
handler, and the option <tt>AUTO_CD</tt> may be used to change to directories
that happen to have MIME suffixes.
</p>
<a name="index-execute_002dnever_002c-MIME-style"></a>
</dd>
<dt><tt>execute-never</tt></dt>
<dd><p>This style is useful in combination with <tt>execute-as-is</tt>. It is
set to an array of patterns corresponding to full paths to files that
should never be treated as executable, even if the file passed to
the MIME handler matches <tt>execute-as-is</tt>. This is useful for file
systems that don’t handle execute permission or that contain executables
from another operating system. For example, if <tt>/mnt/windows</tt> is a
Windows mount, then
</p>
<div class="example">
<pre class="example">zstyle ':mime:*' execute-never '/mnt/windows/*'
</pre></div>
<p>will ensure that any files found in that area will be executed as MIME
types even if they are executable. As this example shows, the complete
file name is matched against the pattern, regardless of how the file
was passed to the handler. The file is resolved to a full path using
the <tt>:A</tt> modifier described in
<a href="Expansion.html#Modifiers">Modifiers</a>;
this means that symbolic links are resolved where possible, so that
links into other file systems behave in the correct fashion.
</p>
<a name="index-file_002dpath_002c-MIME-style"></a>
</dd>
<dt><tt>file-path</tt></dt>
<dd><p>Used if the style <tt>find-file-in-path</tt> is true for the same context.
Set to an array of directories that are used for searching for the
file to be handled; the default is the command path given by the
special parameter <tt>path</tt>. The shell option <tt>PATH_DIRS</tt> is respected;
if that is set, the appropriate path will be searched even if the
name of the file to be handled as it appears on the command line contains
a ‘<tt>/</tt>’.
The full context is <tt>:mime:.</tt><var>suffix</var><tt>:</tt>, as described for the style
<tt>handler</tt>.
</p>
<a name="index-find_002dfile_002din_002dpath_002c-MIME-style"></a>
</dd>
<dt><tt>find-file-in-path</tt></dt>
<dd><p>If set, allows files whose names do not contain absolute paths
to be searched for in the command path or the path specified by the
<tt>file-path</tt> style. If the file is not found in the path, it is looked
for locally (whether or not the current directory is in the path); if it is
not found locally, the handler will abort unless the <tt>handle-nonexistent</tt>
style is set. Files found in the path are tested as described for
the style <tt>execute-as-is</tt>.
The full context is <tt>:mime:.</tt><var>suffix</var><tt>:</tt>, as described for the style
<tt>handler</tt>.
</p>
<a name="index-flags_002c-MIME-style"></a>
</dd>
<dt><tt>flags</tt></dt>
<dd><p>Defines flags to go with a handler; the context is as for the
<tt>handler</tt> style, and the format is as for the flags in <tt>mailcap</tt>.
</p>
<a name="index-handle_002dnonexistent_002c-MIME-style"></a>
</dd>
<dt><tt>handle-nonexistent</tt></dt>
<dd><p>By default, arguments that don’t correspond to files are not passed
to the MIME handler in order to prevent it from intercepting commands found
in the path that happen to have suffixes. This style may be set to
an array of extended glob patterns for arguments that will be passed to the
handler even if they don’t exist. If it is not explicitly set it
defaults to <tt>[[:alpha:]]#:/*</tt> which allows URLs to be passed to the MIME
handler even though they don’t exist in that format in the file system.
The full context is <tt>:mime:.</tt><var>suffix</var><tt>:</tt>, as described for the style
<tt>handler</tt>.
</p>
<a name="index-handler_002c-MIME-style"></a>
</dd>
<dt><tt>handler</tt></dt>
<dd><p>Specifies a handler for a suffix; the suffix is given by the context as
<tt>:mime:.</tt><var>suffix</var><tt>:</tt>, and the format of the handler is exactly
that in <tt>mailcap</tt>. Note in particular the ‘<tt>.</tt>’ and trailing colon
to distinguish this use of the context. This overrides any handler
specified by the <tt>mailcap</tt> files. If the handler requires a terminal,
the <tt>flags</tt> style should be set to include the word <tt>needsterminal</tt>,
or if the output is to be displayed through a pager (but not if the
handler is itself a pager), it should include <tt>copiousoutput</tt>.
</p>
<a name="index-mailcap_002c-MIME-style"></a>
</dd>
<dt><tt>mailcap</tt></dt>
<dd><p>A list of files in the format of <tt>~/.mailcap</tt> and
<tt>/etc/mailcap</tt> to be read during setup, replacing the default list
which consists of those two files. The context is <tt>:mime:</tt>.
A <tt>+</tt> in the list will be replaced by the default files.
</p>
<a name="index-mailcap_002dpriorities_002c-MIME-style"></a>
</dd>
<dt><tt>mailcap-priorities</tt></dt>
<dd><p>This style is used to resolve multiple mailcap entries for the same MIME
type. It consists of an array of the following elements, in descending
order of priority; later entries will be used if earlier entries are
unable to resolve the entries being compared. If none of the tests
resolve the entries, the first entry encountered is retained.
</p>
<dl compact="compact">
<dt><tt>files</tt></dt>
<dd><p>The order of files (entries in the <tt>mailcap</tt> style) read. Earlier
files are preferred. (Note this does not resolve entries in the same file.)
</p>
</dd>
<dt><tt>priority</tt></dt>
<dd><p>The priority flag from the mailcap entry. The priority is an integer
from 0 to 9 with the default value being 5.
</p>
</dd>
<dt><tt>flags</tt></dt>
<dd><p>The test given by the <tt>mailcap-prio-flags</tt> option is used to resolve
entries.
</p>
</dd>
<dt><tt>place</tt></dt>
<dd><p>Later entries are preferred; as the entries are strictly ordered, this
test always succeeds.
</p>
</dd>
</dl>
<p>Note that as this style is handled during initialisation, the context
is always <tt>:mime:</tt>, with no discrimination by suffix.
</p>
<a name="index-mailcap_002dprio_002dflags_002c-MIME-style"></a>
</dd>
<dt><tt>mailcap-prio-flags</tt></dt>
<dd><p>This style is used when the keyword <tt>flags</tt> is encountered in the
list of tests specified by the <tt>mailcap-priorities</tt> style.
It should be set to a list of patterns, each of which is tested against
the flags specified in the mailcap entry (in other words, the sets of
assignments found with some entries in the mailcap file). Earlier
patterns in the list are preferred to later ones, and matched patterns
are preferred to unmatched ones.
</p>
<a name="index-mime_002dtypes_002c-MIME-style"></a>
</dd>
<dt><tt>mime-types</tt></dt>
<dd><p>A list of files in the format of <tt>~/.mime.types</tt> and
<tt>/etc/mime.types</tt> to be read during setup, replacing the default list
which consists of those two files. The context is <tt>:mime:</tt>.
A <tt>+</tt> in the list will be replaced by the default files.
</p>
<a name="index-never_002dbackground_002c-MIME-style"></a>
</dd>
<dt><tt>never-background</tt></dt>
<dd><p>If this boolean style is set, the handler for the given context is
always run in the foreground, even if the flags provided in the mailcap
entry suggest it need not be (for example, it doesn’t require a
terminal).
</p>
<a name="index-pager_002c-MIME-style"></a>
</dd>
<dt><tt>pager</tt></dt>
<dd><p>If set, will be used instead of <tt>$PAGER</tt> or <tt>more</tt> to handle
suffixes where the <tt>copiousoutput</tt> flag is set. The context is
as for <tt>handler</tt>, i.e. <tt>:mime:.</tt><var>suffix</var><tt>:</tt> for handling
a file with the given <var>suffix</var>.
</p>
</dd>
</dl>
<p>Examples:
</p>
<div class="example">
<pre class="example">zstyle ':mime:*' mailcap ~/.mailcap /usr/local/etc/mailcap
zstyle ':mime:.txt:' handler less %s
zstyle ':mime:.txt:' flags needsterminal
</pre></div>
<p>When <tt>zsh-mime-setup</tt> is subsequently run, it will look for
<tt>mailcap</tt> entries in the two files given. Files of suffix <tt>.txt</tt>
will be handled by running ‘<tt>less</tt> <var>file.txt</var>’. The flag
<tt>needsterminal</tt> is set to show that this program must run attached to a
terminal.
</p>
<p>As there are several steps to dispatching a command, the following
should be checked if attempting to execute a file by extension
<tt>.</tt><var>ext</var> does not have the expected effect.
</p>
<p>The command ‘<tt>alias -s</tt> <var>ext</var>’ should show
‘<tt>ps=zsh-mime-handler</tt>’. If it shows something else, another suffix
alias was already installed and was not overwritten. If it shows
nothing, no handler was installed: this is most likely because no
handler was found in the <tt>.mime.types</tt> and <tt>mailcap</tt> combination for
<tt>.ext</tt> files. In that case, appropriate handling should be added to
<tt>~/.mime.types</tt> and <tt>mailcap</tt>.
</p>
<p>If the extension is handled by <tt>zsh-mime-handler</tt> but the file is
not opened correctly, either the handler defined for the type is
incorrect, or the flags associated with it are in appropriate. Running
<tt>zsh-mime-setup -l</tt> will show the handler and, if there are any, the
flags. A <tt>%s</tt> in the handler is replaced by the file (suitably quoted
if necessary). Check that the handler program listed lists and can
be run in the way shown. Also check that the flags <tt>needsterminal</tt> or
<tt>copiousoutput</tt> are set if the handler needs to be run under a
terminal; the second flag is used if the output should be sent to a pager.
An example of a suitable <tt>mailcap</tt> entry for such a program is:
</p>
<div class="example">
<pre class="example">text/html; /usr/bin/lynx '%s'; needsterminal
</pre></div>
<p>Running ‘<tt>zsh-mime-handler -l</tt> <var>command line</var>’ prints the command
line that would be executed, simplified to remove the effect of any
flags, and quoted so that the output can be run as a complete zsh
command line. This is used by the completion system to decide how to
complete after a file handled by <tt>zsh-mime-setup</tt>.
</p>
<a name="index-pick_002dweb_002dbrowser"></a>
</dd>
<dt><tt>pick-web-browser</tt></dt>
<dd><p>This function is separate from the two MIME functions described above
and can be assigned directly to a suffix:
</p>
<div class="example">
<pre class="example">autoload -U pick-web-browser
alias -s html=pick-web-browser
</pre></div>
<p>It is provided as an intelligent front end to dispatch a web browser.
It may be run as either a function or a shell script. The status
255 is returned if no browser could be started.
</p>
<p>Various styles are available to customize the choice of browsers:
</p>
<dl compact="compact">
<dt><tt>browser-style</tt></dt>
<dd><p>The value of the style is an array giving preferences in decreasing order
for the type of browser to use. The values of elements may be
</p>
<dl compact="compact">
<dt><tt>running</tt></dt>
<dd><p>Use a GUI browser that is already running when an X Window display is
available. The browsers listed in the <tt>x-browsers</tt> style are tried
in order until one is found; if it is, the file will be displayed in
that browser, so the user may need to check whether it has appeared.
If no running browser is found, one is not started. Browsers other than
Firefox, Opera and Konqueror are assumed to understand the Mozilla
syntax for opening a URL remotely.
</p>
</dd>
<dt><tt>x</tt></dt>
<dd><p>Start a new GUI browser when an X Window display is available. Search for
the availability of one of the browsers listed in the <tt>x-browsers</tt> style
and start the first one that is found. No check is made for an already
running browser.
</p>
</dd>
<dt><tt>tty</tt></dt>
<dd><p>Start a terminal-based browser. Search for the availability of one
of the browsers listed in the <tt>tty-browsers</tt> style and start the
first one that is found.
</p>
</dd>
</dl>
<p>If the style is not set the default <tt>running x tty</tt> is used.
</p>
</dd>
<dt><tt>x-browsers</tt></dt>
<dd><p>An array in decreasing order
of preference of browsers to use when running under the X Window System.
The array consists of the command name under which to start the
browser. They are looked up in the context <tt>:mime:</tt> (which may
be extended in future, so appending ‘<tt>*</tt>’ is recommended). For
example,
</p>
<div class="example">
<pre class="example">zstyle ':mime:*' x-browsers opera konqueror firefox
</pre></div>
<p>specifies that <tt>pick-web-browser</tt> should first look for a running
instance of Opera, Konqueror or Firefox, in that order, and if it
fails to find any should attempt to start Opera. The default is
<tt>firefox mozilla netscape opera konqueror</tt>.
</p>
</dd>
<dt><tt>tty-browsers</tt></dt>
<dd><p>An array similar to <tt>x-browsers</tt>, except that it gives browsers to
use when no X Window display is available. The default is
<tt>elinks links lynx</tt>.
</p>
</dd>
<dt><tt>command</tt></dt>
<dd><p>If it is set this style is used to pick the command
used to open a page for a browser. The context is
<tt>:mime:browser:new:$browser:</tt> to start a new browser or
<tt>:mime:browser:running:$browser:</tt> to open a URL in a browser already
running on the current X display, where <tt>$browser</tt> is the value matched
in the <tt>x-browsers</tt> or <tt>tty-browsers</tt> style. The escape sequence
<tt>%b</tt> in the style’s value will be replaced by the browser, while <tt>%u</tt>
will be replaced by the URL. If the style is not set, the default for all
new instances is equivalent to <tt>%b %u</tt> and the defaults for using running
browsers are equivalent to the values <tt>kfmclient openURL %u</tt> for
Konqueror, <tt>firefox -new-tab %u</tt> for Firefox, <tt>opera -newpage %u</tt>
for Opera, and <tt>%b -remote "openUrl(%u)"</tt> for all others.
</p>
</dd>
</dl>
</dd>
</dl>
<hr>
<a name="Mathematical-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#MIME-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#User-Configuration-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Mathematical-Functions-1"></a>
<h2 class="section">26.9 Mathematical Functions</h2>
<dl compact="compact">
<dd><a name="index-zcalc"></a>
</dd>
<dt><tt>zcalc</tt> [ <tt>-ef</tt> ] [ <var>expression</var> ... ]</dt>
<dd><p>A reasonably powerful calculator based on zsh’s arithmetic evaluation
facility. The syntax is similar to that of formulae in most programming
languages; see
<a href="Arithmetic-Evaluation.html#Arithmetic-Evaluation">Arithmetic Evaluation</a> for details.
</p>
<p>Non-programmers should note that, as in many other programming
languages, expressions involving only integers (whether constants
without a ‘<tt>.</tt>’, variables containing such constants as strings, or
variables declared to be integers) are by default evaluated using
integer arithmetic, which is not how an ordinary desk calculator
operates. To force floating point operation, pass the option <tt>-f</tt>;
see further notes below.
</p>
<p>The mathematical library <tt>zsh/mathfunc</tt> will be loaded if it is
available; see
<a href="Zsh-Modules.html#The-zsh_002fmathfunc-Module">The zsh/mathfunc Module</a>. The mathematical functions
correspond to the raw system libraries, so trigonometric functions are
evaluated using radians, and so on.
</p>
<p>Each line typed is evaluated as an expression. The prompt shows a number,
which corresponds to a positional parameter where the result of that
calculation is stored. For example, the result of the calculation on the
line preceded by ‘<tt>4> </tt>’ is available as <tt>$4</tt>. The last value
calculated is available as <tt>ans</tt>. Full command line editing, including
the history of previous calculations, is available; the history is saved in
the file <tt>~/.zcalc_history</tt>. To exit, enter a blank line or type ‘<tt>:q</tt>’
on its own (‘<tt>q</tt>’ is allowed for historical compatibility).
</p>
<p>A line ending with a single backslash is treated in the same fashion
as it is in command line editing: the backslash is removed, the
function prompts for more input (the prompt is preceded by ‘<tt>...</tt>’
to indicate this), and the lines are combined into one to get the final
result. In addition, if the input so far contains more open than
close parentheses <tt>zcalc</tt> will prompt for more input.
</p>
<p>If arguments are given to <tt>zcalc</tt> on start up, they are used to prime the
first few positional parameters. A visual indication of this is given when
the calculator starts.
</p>
<p>The constants <tt>PI</tt> (3.14159...) and <tt>E</tt> (2.71828...) are provided.
Parameter assignment is possible, but note that all parameters will be put
into the global namespace.
</p>
<p>The output base can be initialised by passing the option ‘<tt>-#</tt><var>base</var>’,
for example ‘<tt>zcalc -#16</tt>’ (the ‘<tt>#</tt>’ may have to be quoted, depending
on the globbing options set).
</p>
<p>If the option ‘<tt>-e</tt>’ is set, the function runs non-interactively:
the arguments are treated as expressions to be evaluated as if entered
interactively line by line.
</p>
<p>If the option ‘<tt>-f</tt>’ is set, all numbers are treated as floating
point, hence for example the expression ‘<tt>3/4</tt>’ evaluates to 0.75
rather than 0. Options must appear in separate words.
</p>
<p>The prompt is configurable via the parameter <tt>ZCALCPROMPT</tt>, which
undergoes standard prompt expansion. The index of the current entry is
stored locally in the first element of the array <tt>psvar</tt>, which can be
referred to in <tt>ZCALCPROMPT</tt> as ‘<tt>%1v</tt>’. The default prompt is
‘<tt>%1v> </tt>’.
</p>
<p>A few special commands are available; these are introduced by a colon.
For backward compatibility, the colon may be omitted for certain
commands. Completion is available if <tt>compinit</tt> has been run.
</p>
<p>The output precision may be specified within zcalc by special commands
familiar from many calculators.
</p><dl compact="compact">
<dt><tt>:norm</tt></dt>
<dd><p>The default output format. It corresponds to the printf <tt>%g</tt>
specification. Typically this shows six decimal digits.
</p>
</dd>
<dt><tt>:sci</tt> <var>digits</var></dt>
<dd><p>Scientific notation, corresponding to the printf <tt>%g</tt> output format with
the precision given by <var>digits</var>. This produces either fixed point or
exponential notation depending on the value output.
</p>
</dd>
<dt><tt>:fix</tt> <var>digits</var></dt>
<dd><p>Fixed point notation, corresponding to the printf <tt>%f</tt> output format with
the precision given by <var>digits</var>.
</p>
</dd>
<dt><tt>:eng</tt> <var>digits</var></dt>
<dd><p>Exponential notation, corresponding to the printf <tt>%E</tt> output format with
the precision given by <var>digits</var>.
</p>
</dd>
<dt><tt>:raw</tt></dt>
<dd><p>Raw output: this is the default form of the output from a math
evaluation. This may show more precision than the number actually
possesses.
</p>
</dd>
</dl>
<p>Other special commands:
</p><dl compact="compact">
<dt><tt>:!</tt><var>line...</var></dt>
<dd><p>Execute <var>line...</var> as a normal shell command line. Note that it
is executed in the context of the function, i.e. with local variables.
Space is optional after <tt>:!</tt>.
</p>
</dd>
<dt><tt>:local</tt> <var>arg</var> ...</dt>
<dd><p>Declare variables local to the function. Note that certain variables
are used by the function for its own purposes. Other variables
may be used, too, but they will be taken from or put into the global
scope.
</p>
</dd>
<dt><tt>:function</tt> <var>name</var> [ <var>body</var> ]</dt>
<dd><p>Define a mathematical function or (with no <var>body</var>) delete it.
<tt>:function</tt> may be abbreviated to <tt>:func</tt> or simply <tt>:f</tt>.
The <var>name</var> may contain the same characters as a shell function name.
The function is defined using <tt>zmathfuncdef</tt>, see below.
</p>
<p>Note that <tt>zcalc</tt> takes care of all quoting. Hence for example:
</p>
<div class="example">
<pre class="example">:f cube $1 * $1 * $1
</pre></div>
<p>defines a function to cube the sole argument.
</p>
</dd>
<dt><tt>[#</tt><var>base</var><tt>]</tt></dt>
<dd><p>This is not a special command, rather part of normal arithmetic
syntax; however, when this form appears on a line by itself the default
output radix is set to <var>base</var>. Use, for example, ‘<tt>[#16]</tt>’ to display
hexadecimal output preceded by an indication of the base, or ‘<tt>[##16]</tt>’
just to display the raw number in the given base. Bases themselves are
always specified in decimal. ‘<tt>[#]</tt>’ restores the normal output format.
Note that setting an output base suppresses floating point output; use
‘<tt>[#]</tt>’ to return to normal operation.
</p>
</dd>
</dl>
<p>See the comments in the function for a few extra tips.
</p>
<a name="index-zmathfuncdef"></a>
</dd>
<dt><tt>zmathfuncdef</tt> [ <var>mathfunc</var> [ <var>body</var> ] ]</dt>
<dd><p>A convenient front end to <tt>functions -M</tt>.
</p>
<p>With two arguments, define a mathematical function named <var>mathfunc</var>
which can be used in any form of arithmetic evaluation. <var>body</var>
is a mathematical expression to implement the function. It may
contain references to position parameters <tt>$1</tt>, <tt>$2</tt>, ...
to refer to mandatory parameters and <tt>${1:-</tt><var>defvalue</var><tt>}</tt> ...
to refer to optional parameters. Note that the forms must be
strictly adhered to for the function to calculate the correct number
of arguments. The implementation is held in a shell function named
<tt>zsh_math_func_</tt><var>mathfunc</var>; usually the user will not need
to refer to the shell function directly. Any existing function
of the same name is silently replaced.
</p>
<p>With one argument, remove the mathematical function <var>mathfunc</var>
as well as the shell function implementation.
</p>
<p>With no arguments, list all <var>mathfunc</var> functions in a form
suitable for restoring the definition.
The functions have not necessarily been defined by <tt>zmathfuncdef</tt>.
</p>
</dd>
</dl>
<hr>
<a name="User-Configuration-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Mathematical-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Other-Functions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="User-Configuration-Functions-1"></a>
<h2 class="section">26.10 User Configuration Functions</h2>
<p>The <tt>zsh/newuser</tt> module comes with a function to aid in configuring
shell options for new users. If the module is installed, this function can
also be run by hand. It is available even if the module’s default
behaviour, namely running the function for a new user logging in without
startup files, is inhibited.
</p>
<dl compact="compact">
<dt><tt>zsh-newuser-install</tt> [ <tt>-f</tt> ]</dt>
<dd><p>The function presents the user with various options for customizing
their initialization scripts. Currently only <tt>~/.zshrc</tt> is handled.
<tt>$ZDOTDIR/.zshrc</tt> is used instead if the parameter <tt>ZDOTDIR</tt> is
set; this provides a way for the user to configure a file without
altering an existing <tt>.zshrc</tt>.
</p>
<p>By default the function exits immediately if it finds any of the files
<tt>.zshenv</tt>, <tt>.zprofile</tt>, <tt>.zshrc</tt>, or <tt>.zlogin</tt> in the appropriate
directory. The option <tt>-f</tt> is required in order to force the function
to continue. Note this may happen even if <tt>.zshrc</tt> itself does not
exist.
</p>
<p>As currently configured, the function will exit immediately if the
user has root privileges; this behaviour cannot be overridden.
</p>
<p>Once activated, the function’s behaviour is supposed to be
self-explanatory. Menus are present allowing the user to alter
the value of options and parameters. Suggestions for improvements are
always welcome.
</p>
<p>When the script exits, the user is given the opportunity to save the new
file or not; changes are not irreversible until this point. However,
the script is careful to restrict changes to the file only to a group
marked by the lines ‘<tt># Lines configured by zsh-newuser-install</tt>’ and
‘<tt># End of lines configured by zsh-newuser-install</tt>’. In addition,
the old version of <tt>.zshrc</tt> is saved to a file with the suffix
<tt>.zni</tt> appended.
</p>
<p>If the function edits an existing <tt>.zshrc</tt>, it is up to the user
to ensure that the changes made will take effect. For example, if
control usually returns early from the existing <tt>.zshrc</tt> the lines
will not be executed; or a later initialization file may override
options or parameters, and so on. The function itself does not attempt to
detect any such conflicts.
</p>
</dd>
</dl>
<hr>
<a name="Other-Functions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#User-Configuration-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#User-Contributions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Descriptions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Other-Functions-1"></a>
<h2 class="section">26.11 Other Functions</h2>
<p>There are a large number of helpful functions in the <tt>Functions/Misc</tt>
directory of the zsh distribution. Most are very simple and do not
require documentation here, but a few are worthy of special mention.
</p>
<hr>
<a name="Descriptions"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Other-Functions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Other-Functions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="#Styles-2" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.11.1 Descriptions</h3>
<dl compact="compact">
<dd><a name="index-colors"></a>
</dd>
<dt><tt>colors</tt></dt>
<dd><p>This function initializes several associative arrays to map color names to
(and from) the ANSI standard eight-color terminal codes. These are used
by the prompt theme system (<a href="#Prompt-Themes">Prompt Themes</a>). You seldom should need to run
<tt>colors</tt> more than once.
</p>
<p>The eight base colors are: <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>,
<tt>blue</tt>, <tt>magenta</tt>, <tt>cyan</tt>, and <tt>white</tt>. Each of these has codes for
foreground and background. In addition there are seven intensity attributes:
<tt>bold</tt>, <tt>faint</tt>, <tt>standout</tt>, <tt>underline</tt>, <tt>blink</tt>, <tt>reverse</tt>,
and <tt>conceal</tt>. Finally, there are seven codes used to negate attributes:
<tt>none</tt> (reset all attributes to the defaults), <tt>normal</tt>
(neither bold nor faint), <tt>no-standout</tt>, <tt>no-underline</tt>, <tt>no-blink</tt>,
<tt>no-reverse</tt>, and <tt>no-conceal</tt>.
</p>
<p>Some terminals do not support all combinations of colors and intensities.
</p>
<p>The associative arrays are:
</p>
<dl compact="compact">
<dt><tt>color</tt></dt>
<dt><tt>colour</tt></dt>
<dd><p>Map all the color names to their integer codes, and integer codes to the
color names. The eight base names map to the foreground color codes, as
do names prefixed with ‘<tt>fg-</tt>’, such as ‘<tt>fg-red</tt>’. Names prefixed
with ‘<tt>bg-</tt>’, such as ‘<tt>bg-blue</tt>’, refer to the background codes. The
reverse mapping from code to color yields base name for foreground codes
and the <tt>bg-</tt> form for backgrounds.
</p>
<p>Although it is a misnomer to call them ‘colors’, these arrays also map the
other fourteen attributes from names to codes and codes to names.
</p>
</dd>
<dt><tt>fg</tt></dt>
<dt><tt>fg_bold</tt></dt>
<dt><tt>fg_no_bold</tt></dt>
<dd><p>Map the eight basic color names to ANSI terminal escape sequences that set
the corresponding foreground text properties. The <tt>fg</tt> sequences change
the color without changing the eight intensity attributes.
</p>
</dd>
<dt><tt>bg</tt></dt>
<dt><tt>bg_bold</tt></dt>
<dt><tt>bg_no_bold</tt></dt>
<dd><p>Map the eight basic color names to ANSI terminal escape sequences that set
the corresponding background properties. The <tt>bg</tt> sequences change the
color without changing the eight intensity attributes.
</p>
</dd>
</dl>
<p>In addition, the scalar parameters <tt>reset_color</tt> and <tt>bold_color</tt> are
set to the ANSI terminal escapes that turn off all attributes and turn on
bold intensity, respectively.
</p>
<a name="index-fned"></a>
</dd>
<dt><tt>fned</tt> [ <tt>-x</tt> <var>num</var> ] <var>name</var></dt>
<dd><p>Same as <tt>zed -f</tt>. This function does not appear in the zsh
distribution, but can be created by linking <tt>zed</tt> to the name <tt>fned</tt>
in some directory in your <tt>fpath</tt>.
</p>
<a name="index-is_002dat_002dleast"></a>
</dd>
<dt><tt>is-at-least</tt> <var>needed</var> [ <var>present</var> ]</dt>
<dd><p>Perform a greater-than-or-equal-to comparison of two strings having the
format of a zsh version number; that is, a string of numbers and text with
segments separated by dots or dashes. If the <var>present</var> string is not
provided, <tt>$ZSH_VERSION</tt> is used. Segments are paired left-to-right in
the two strings with leading non-number parts ignored. If one string has
fewer segments than the other, the missing segments are considered zero.
</p>
<p>This is useful in startup files to set options and other state that are
not available in all versions of zsh.
</p>
<div class="example">
<pre class="example">is-at-least 3.1.6-15 && setopt NO_GLOBAL_RCS
is-at-least 3.1.0 && setopt HIST_REDUCE_BLANKS
is-at-least 2.6-17 || print "You can't use is-at-least here."
</pre></div>
<a name="index-nslookup"></a>
</dd>
<dt><tt>nslookup</tt> [ <var>arg</var> ... ]</dt>
<dd><p>This wrapper function for the <tt>nslookup</tt> command requires the
<tt>zsh/zpty</tt> module (see
<a href="Zsh-Modules.html#The-zsh_002fzpty-Module">The zsh/zpty Module</a>). It behaves exactly like the standard <tt>nslookup</tt>
except that it provides customizable prompts (including a right-side
prompt) and completion of nslookup commands, host names, etc. (if you use
the function-based completion system). Completion styles may be set with
the context prefix ‘<tt>:completion:nslookup</tt>’.
</p>
<p>See also the <tt>pager</tt>, <tt>prompt</tt> and <tt>rprompt</tt> styles below.
</p>
<a name="index-regexp_002dreplace"></a>
</dd>
<dt><tt>regexp-replace</tt> <var>var</var> <var>regexp</var> <var>replace</var></dt>
<dd><p>Use regular expressions to perform a global search and replace operation
on a variable. If the option <tt>RE_MATCH_PCRE</tt> is not set, POSIX
extended regular expressions are used, else Perl-compatible regular
expressions (this requires the shell to be linked against the <tt>pcre</tt>
library).
</p>
<p><var>var</var> is the name of the variable containing the string to be matched.
The variable will be modified directly by the function. The
variables <tt>MATCH</tt>, <tt>MBEGIN</tt>, <tt>MEND</tt>, <tt>match</tt>, <tt>mbegin</tt>, <tt>mend</tt>
should be avoided as these are used by the regular expression code.
</p>
<p><var>regexp</var> is the regular expression to match against the string.
</p>
<p><var>replace</var> is the replacement text. This can contain parameter, command
and arithmetic expressions which will be replaced: in particular, a
reference to <tt>$MATCH</tt> will be replaced by the text matched by the pattern.
</p>
<p>The return status is 0 if at least one match was performed, else 1.
</p>
<a name="index-run_002dhelp"></a>
</dd>
<dt><tt>run-help</tt> <var>cmd</var></dt>
<dd><p>This function is designed to be invoked by the <tt>run-help</tt> ZLE widget,
in place of the default alias. See ‘Accessing On-Line Help’
(<a href="#Utilities">Utilities</a>) for setup instructions.
</p>
<p>In the discussion which follows, if <var>cmd</var> is a file system path, it is
first reduced to its rightmost component (the file name).
</p>
<p>Help is first sought by looking for a file named <var>cmd</var> in the directory
named by the <tt>HELPDIR</tt> parameter. If no file is found, an assistant
function, alias, or command named <tt>run-help-<var>cmd</var></tt> is sought. If
found, the assistant is executed with the rest of the current command line
(everything after the command name <var>cmd</var>) as its arguments. When
neither file nor assistant is found, the external command
‘<tt>man</tt> <var>cmd</var>’ is run.
</p>
<p>An example assistant for the "ssh" command:
</p>
<div class="example">
<pre class="example">run-help-ssh() {
emulate -LR zsh
local -a args
# Delete the "-l username" option
zparseopts -D -E -a args l:
# Delete other options, leaving: host command
args=(${@:#-*})
if [[ ${#args} -lt 2 ]]; then
man ssh
else
run-help $args[2]
fi
}
</pre></div>
<p>Several of these assistants are provided in the <tt>Functions/Misc</tt>
directory. These must be autoloaded, or placed as executable scripts in
your search path, in order to be found and used by <tt>run-help</tt>.
</p>
<dl compact="compact">
<dd><a name="index-run_002dhelp_002dgit"></a>
<a name="index-run_002dhelp_002dsvk"></a>
<a name="index-run_002dhelp_002dsvn"></a>
</dd>
<dt><tt>run-help-git</tt></dt>
<dt><tt>run-help-svk</tt></dt>
<dt><tt>run-help-svn</tt></dt>
<dd><p>Assistant functions for the <tt>git</tt>, <tt>svk</tt>, and <tt>svn</tt> commands.
</p>
</dd>
</dl>
</dd>
<dt><tt>tetris</tt></dt>
<dd><p>Zsh was once accused of not being as complete as Emacs,
because it lacked a Tetris game. This function was written to
refute this vicious slander.
</p>
<p>This function must be used as a ZLE widget:
</p>
<div class="example">
<pre class="example">autoload -U tetris
zle -N tetris
bindkey <var>keys</var> tetris
</pre></div>
<p>To start a game, execute the widget by typing the <var>keys</var>. Whatever command
line you were editing disappears temporarily, and your keymap is also
temporarily replaced by the Tetris control keys. The previous editor state
is restored when you quit the game (by pressing ‘<tt>q</tt>’) or when you lose.
</p>
<p>If you quit in the middle of a game, the next invocation of the <tt>tetris</tt>
widget will continue where you left off. If you lost, it will start a new
game.
</p>
</dd>
<dt><tt>tetriscurses</tt></dt>
<dd><p>This is a port of the above to zcurses. The input handling is improved
a bit so that moving a block sideways doesn’t automatically advance a
timestep, and the graphics use unicode block graphics.
</p>
<p>This version does not save the game state between invocations, and is not
invoked as a widget, but rather as:
</p>
<div class="example">
<pre class="example">autoload -U tetriscurses
tetriscurses
</pre></div>
<a name="index-zargs"></a>
</dd>
<dt><tt>zargs</tt> [ <var>option</var> ... <tt>-</tt><tt>-</tt> ] [ <var>input</var> ... ] [ <tt>-</tt><tt>-</tt> <var>command</var> [ <var>arg</var> ... ] ]</dt>
<dd><p>This function has a similar purpose to GNU xargs. Instead of
reading lines of arguments from the standard input, it takes them from
the command line. This is useful because zsh, especially with recursive
glob operators, often can construct a command line for a shell function
that is longer than can be accepted by an external command.
</p>
<p>The <var>option</var> list represents options of the <tt>zargs</tt> command itself,
which are the same as those of <tt>xargs</tt>. The <var>input</var> list is the
collection of strings (often file names) that become the arguments of the
<tt>command</tt>, analogous to the standard input of <tt>xargs</tt>. Finally, the
<var>arg</var> list consists of those arguments (usually options) that are
passed to the <var>command</var> each time it runs. The <var>arg</var> list precedes
the elements from the <tt>input</tt> list in each run. If no <var>command</var> is
provided, then no <var>arg</var> list may be provided, and in that event the
default command is ‘<tt>print</tt>’ with arguments ‘<tt>-r -</tt><tt>-</tt>’.
</p>
<p>For example, to get a long <tt>ls</tt> listing of all plain files in the
current directory or its subdirectories:
</p>
<div class="example">
<pre class="example">autoload -U zargs
zargs -- **/*(.) -- ls -l
</pre></div>
<p>Note that ‘<tt>-</tt><tt>-</tt>’ is used both to mark the end of the <var>option</var>
list and to mark the end of the <var>input</var> list, so it must appear twice
whenever the <var>input</var> list may be empty. If there is guaranteed to be
at least one <var>input</var> and the first <var>input</var> does not begin with a
‘<tt>-</tt>’, then the first ‘<tt>-</tt><tt>-</tt>’ may be omitted.
</p>
<p>In the event that the string ‘<tt>-</tt><tt>-</tt>’ is or may be an <var>input</var>, the
<tt>-e</tt> option may be used to change the end-of-inputs marker. Note that
this does <em>not</em> change the end-of-options marker. For example, to use
‘<tt>..</tt>’ as the marker:
</p>
<div class="example">
<pre class="example">zargs -e.. -- **/*(.) .. ls -l
</pre></div>
<p>This is a good choice in that example because no plain file can be named
‘<tt>..</tt>’, but the best end-marker depends on the circumstances.
</p>
<p>The options <tt>-i</tt>, <tt>-I</tt>, <tt>-l</tt>, <tt>-L</tt>, and <tt>-n</tt> differ slightly
from their usage in <tt>xargs</tt>. There are no input lines for <tt>zargs</tt> to
count, so <tt>-l</tt> and <tt>-L</tt> count through the <var>input</var> list, and <tt>-n</tt>
counts the number of arguments passed to each execution of <var>command</var>,
<em>including</em> any <var>arg</var> list. Also, any time <tt>-i</tt> or <tt>-I</tt> is used,
each <var>input</var> is processed separately as if by ‘<tt>-L</tt> <tt>1</tt>’.
</p>
<p>For details of the other <tt>zargs</tt> options, see man page xargs(1) (but note
the difference in function between <tt>zargs</tt> and <tt>xargs</tt>) or run
<tt>zargs</tt> with the <tt>-</tt><tt>-help</tt> option.
</p>
<a name="index-zed"></a>
</dd>
<dt><tt>zed</tt> [ <tt>-f</tt> [ <tt>-x</tt> <var>num</var> ] ] <var>name</var></dt>
<dt><tt>zed -b</tt></dt>
<dd><p>This function uses the ZLE editor to edit a file or function.
</p>
<p>Only one <var>name</var> argument is allowed.
If the <tt>-f</tt> option is given, the name is taken to be that of
a function; if the function is marked for autoloading, <tt>zed</tt> searches
for it in the <tt>fpath</tt> and loads it. Note that functions edited this way
are installed into the current shell, but <em>not</em> written back to the
autoload file. In this case the <tt>-x</tt> option specifies that leading
tabs indenting the function according to syntax should be converted into
the given number of spaces; ‘<tt>-x 2</tt>’ is consistent with the layout
of functions distributed with the shell.
</p>
<p>Without <tt>-f</tt>, <var>name</var> is the path name of the file to edit, which need
not exist; it is created on write, if necessary.
</p>
<p>While editing, the function sets the main keymap to <tt>zed</tt> and the
vi command keymap to <tt>zed-vicmd</tt>. These will be copied from the existing
<tt>main</tt> and <tt>vicmd</tt> keymaps if they do not exist the first time <tt>zed</tt>
is run. They can be used to provide special key bindings used only in zed.
</p>
<p>If it creates the keymap, <tt>zed</tt> rebinds the return key to insert a line
break and ‘<tt>^X^W</tt>’ to accept the edit in the <tt>zed</tt> keymap, and binds
‘<tt>ZZ</tt>’ to accept the edit in the <tt>zed-vicmd</tt> keymap.
</p>
<p>The bindings alone can be installed by running ‘<tt>zed -b</tt>’. This is
suitable for putting into a startup file. Note that, if rerun,
this will overwrite the existing <tt>zed</tt> and <tt>zed-vicmd</tt> keymaps.
</p>
<p>Completion is available, and styles may be set with the context prefix
‘<tt>:completion:zed</tt>’.
</p>
<p>A zle widget <tt>zed-set-file-name</tt> is available. This can be called by
name from within zed using ‘<tt>\ex zed-set-file-name</tt>’ (note, however, that
because of zed’s rebindings you will have to type <tt>^j</tt> at the end instead
of the return key), or can be bound to a key in either of the <tt>zed</tt> or
<tt>zed-vicmd</tt> keymaps after ‘<tt>zed -b</tt>’ has been run. When the widget is
called, it prompts for a new name for the file being edited. When zed
exits the file will be written under that name and the original file will
be left alone. The widget has no effect with ‘<tt>zed -f</tt>’.
</p>
<p>While <tt>zed-set-file-name</tt> is running, zed uses the keymap
<tt>zed-normal-keymap</tt>, which is linked from the main keymap in effect
at the time zed initialised its bindings. (This is to make the return key
operate normally.) The result is that if the main keymap has been changed,
the widget won’t notice. This is not a concern for most users.
</p>
<a name="index-zcp"></a>
<a name="index-zln"></a>
</dd>
<dt><tt>zcp</tt> [ <tt>-finqQvwW</tt> ] <var>srcpat</var> <var>dest</var></dt>
<dt><tt>zln</tt> [ <tt>-finqQsvwW</tt> ] <var>srcpat</var> <var>dest</var></dt>
<dd><p>Same as <tt>zmv -C</tt> and <tt>zmv -L</tt>, respectively. These functions do not
appear in the zsh distribution, but can be created by linking <tt>zmv</tt> to
the names <tt>zcp</tt> and <tt>zln</tt> in some directory in your <tt>fpath</tt>.
</p>
</dd>
<dt><tt>zkbd</tt></dt>
<dd><p>See ‘Keyboard Definition’
(<a href="#Utilities">Utilities</a>).
</p>
<a name="index-zmv"></a>
</dd>
<dt><tt>zmv</tt> [ <tt>-finqQsvwW</tt> ] [ <tt>-C</tt> | <tt>-L</tt> | <tt>-M</tt> | -{<tt>p</tt>|<tt>P</tt>} <var>program</var> ] [ <tt>-o</tt> <var>optstring</var> ]</dt>
<dt><tt> </tt><var>srcpat</var> <var>dest</var></dt>
<dd><p>Move (usually, rename) files matching the pattern <var>srcpat</var> to
corresponding files having names of the form given by <var>dest</var>, where
<var>srcpat</var> contains parentheses surrounding patterns which will be
replaced in turn by <tt>$1</tt>, <tt>$2</tt>, ... in <var>dest</var>. For example,
</p>
<div class="example">
<pre class="example">zmv '(*).lis' '$1.txt'
</pre></div>
<p>renames ‘<tt>foo.lis</tt>’ to ‘<tt>foo.txt</tt>’, ‘<tt>my.old.stuff.lis</tt>’ to
‘<tt>my.old.stuff.txt</tt>’, and so on.
</p>
<p>The pattern is always treated as an <tt>EXTENDED_GLOB</tt> pattern. Any file
whose name is not changed by the substitution is simply ignored. Any
error (a substitution resulted in an empty string, two substitutions gave
the same result, the destination was an existing regular file and <tt>-f</tt>
was not given) causes the entire function to abort without doing
anything.
</p>
<p>In addition to pattern replacement, the variable <tt>$f</tt> can be referrred
to in the second (replacement) argument. This makes it possible to
use variable substitution to alter the argument; see examples below.
</p>
<p>Options:
</p>
<dl compact="compact">
<dt><tt>-f</tt></dt>
<dd><p>Force overwriting of destination files. Not currently
passed down to the <tt>mv</tt>/<tt>cp</tt>/<tt>ln</tt> command due to vagaries of
implementations (but you can use <tt>-o-f</tt> to do that).
</p></dd>
<dt><tt>-i</tt></dt>
<dd><p>Interactive: show each line to be executed and ask the user
whether to execute it. ‘<tt>Y</tt>’ or ‘<tt>y</tt>’ will execute it, anything else will
skip it. Note that you just need to type one character.
</p></dd>
<dt><tt>-n</tt></dt>
<dd><p>No execution: print what would happen, but don’t do it.
</p></dd>
<dt><tt>-q</tt></dt>
<dd><p>Turn bare glob qualifiers off: now assumed by default, so
this has no effect.
</p></dd>
<dt><tt>-Q</tt></dt>
<dd><p>Force bare glob qualifiers on. Don’t turn this on unless
you are actually using glob qualifiers in a pattern.
</p></dd>
<dt><tt>-s</tt></dt>
<dd><p>Symbolic, passed down to <tt>ln</tt>; only works with <tt>-L</tt>.
</p></dd>
<dt><tt>-v</tt></dt>
<dd><p>Verbose: print each command as it’s being executed.
</p></dd>
<dt><tt>-w</tt></dt>
<dd><p>Pick out wildcard parts of the pattern, as described above,
and implicitly add parentheses for referring to them.
</p></dd>
<dt><tt>-W</tt></dt>
<dd><p>Just like <tt>-w</tt>, with the addition of turning wildcards in
the replacement pattern into sequential <tt>${1}</tt> .. <tt>${N}</tt> references.
</p></dd>
<dt><tt>-C</tt></dt>
<dt><tt>-L</tt></dt>
<dt><tt>-M</tt></dt>
<dd><p>Force <tt>cp</tt>, <tt>ln</tt> or <tt>mv</tt>, respectively, regardless of
the name of the function.
</p></dd>
<dt><tt>-p</tt> <var>program</var></dt>
<dd><p>Call <var>program</var> instead of <tt>cp</tt>, <tt>ln</tt> or
<tt>mv</tt>. Whatever it does, it should at least understand the form
</p><div class="example">
<pre class="example"><var>program</var> <tt>-</tt><tt>-</tt> <var>oldname</var> <var>newname</var>
</pre></div>
<p>where <var>oldname</var> and <var>newname</var> are filenames generated by <tt>zmv</tt>.
<var>program</var> will be split into words, so might be e.g. the name
of an archive tool plus a copy or rename subcommand.
</p></dd>
<dt><tt>-P</tt> <var>program</var></dt>
<dd><p>As <tt>-p</tt> <var>program</var>, except that
<var>program</var> does not accept a following <tt>-</tt><tt>-</tt> to indicate the
end of options. In this case filenames must already be in a sane
form for the program in question.
</p></dd>
<dt><tt>-o</tt> <var>optstring</var></dt>
<dd><p>The <var>optstring</var> is split into words and
passed down verbatim to the <tt>cp</tt>, <tt>ln</tt> or <tt>mv</tt> command called to
perform the work. It should probably begin with a ‘<tt>-</tt>’.
</p></dd>
</dl>
<p>Further examples:
</p>
<div class="example">
<pre class="example">zmv -v '(* *)' '${1// /_}'
</pre></div>
<p>For any file in the current directory with at least one space in the name,
replace every space by an underscore and display the commands executed.
</p>
<div class="example">
<pre class="example">zmv -v '* *' '${f// /_}'
</pre></div>
<p>This does exactly the same by referring to the file name stored in <tt>$f</tt>.
</p>
<p>For more complete examples and other implementation details, see the
<tt>zmv</tt> source file, usually located in one of the directories named in
your <tt>fpath</tt>, or in <tt>Functions/Misc/zmv</tt> in the zsh distribution.
</p>
</dd>
<dt><tt>zrecompile</tt></dt>
<dd><p>See ‘Recompiling Functions’
(<a href="#Utilities">Utilities</a>).
</p>
<a name="index-zstyle_002b"></a>
</dd>
<dt><tt>zstyle+</tt> <var>context</var> <var>style</var> <var>value</var> [ <tt>+</tt> <var>subcontext</var> <var>style</var> <var>value</var> ... ]</dt>
<dd><p>This makes defining styles a bit simpler by using a single ‘<tt>+</tt>’ as a
special token that allows you to append a context name to the previously
used context name. Like this:
</p>
<div class="example">
<pre class="example">zstyle+ ':foo:bar' <var>style1</var> <var>value1</var> \
+':baz' <var>style2</var> <var>value2</var> \
+':frob' <var>style3</var> <var>value3</var>
</pre></div>
<p>This defines <var>style1</var> with <var>value1</var> for the context <tt>:foo:bar</tt> as usual,
but it also defines <var>style2</var> with <var>value2</var> for the context
<tt>:foo:bar:baz</tt> and <var>style3</var> with <var>value3</var> for <tt>:foo:bar:frob</tt>. Any
<var>subcontext</var> may be the empty string to re-use the first context
unchanged.
</p>
</dd>
</dl>
<hr>
<a name="Styles-2"></a>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Descriptions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Other-Functions" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">26.11.2 Styles</h3>
<dl compact="compact">
<dd><a name="index-insert_002dtab_002c-completion-style-1"></a>
</dd>
<dt><tt>insert-tab</tt></dt>
<dd><p>The <tt>zed</tt> function <em>sets</em> this style in context ‘<tt>:completion:zed:*</tt>’
to turn off completion when <tt>TAB</tt> is typed at the beginning of a line.
You may override this by setting your own value for this context and style.
</p>
<a name="index-pager_002c-nslookup-style"></a>
</dd>
<dt><tt>pager</tt></dt>
<dd><p>The <tt>nslookup</tt> function looks up this style in the context
‘<tt>:nslookup</tt>’ to determine the program used to display output that does
not fit on a single screen.
</p>
<a name="index-prompt_002c-nslookup-style"></a>
<a name="index-rprompt_002c-nslookup-style"></a>
</dd>
<dt><tt>prompt</tt></dt>
<dt><tt>rprompt</tt></dt>
<dd><p>The <tt>nslookup</tt> function looks up this style in the context
‘<tt>:nslookup</tt>’ to set the prompt and the right-side prompt, respectively.
The usual expansions for the <tt>PS1</tt> and <tt>RPS1</tt> parameters may be used
(see
<a href="Prompt-Expansion.html#Prompt-Expansion">Prompt Expansion</a>).
</p>
</dd>
</dl>
<hr>
<table class="header" cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#User-Contributions" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="zsh_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="Concept-Index.html#Concept-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="zsh_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<p><font size="-1">
This document was generated on <em>September 10, 2018</em> using <a href="http://www.gnu.org/software/texinfo/"><em>texi2any</em></a>.
</font></p>
<font size="-1">Zsh version 5.1.1, released on September 11, 2015.</font>
</body>
</html>
|