text:
Menus Menu Item Menu Item Alias
From Joomla! Documentation
Revision as of 09:45, 22 October 2012 by Piggydoughnut (Talk | contribs)
Menu Manager: Alias Menu Item
How To Access
To create a new Alias Menu Item:
- Select Menus › [name of the menu] from the drop-down menu on the back-end of your Joomla! installation (for example, Menus › Main Menu).
- Click New to create a new menu item.
- Click the Menu Item Type Select button and then click the "Menu Item Alias".(Second last item in the list)
To edit an existing Single Article Menu Item, click its Title in Menu Manager: Menu Items.
- The "Menu Item Alias Create an alias to another menu item" is a link on existing site on your website.
- You can navigte from one Item manu to the site, which you already have in different Item menu.
Quick Tips
Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.
At the top right you will see the toolbar:
The functions are:
- Save: Saves the menu item and stays in the current screen.</translate>
- Save & Close. Saves the menu item and closes the current screen.</translate>
- Save & New. Saves the menu item and keeps the editing screen open and ready to create another menu item.</translate>
- Cancel/Close. Closes the current screen and returns to the previous screen without saving any modifications you may have made.</translate>
- Help. Opens this help screen.</translate>


text:
Leadership elections bring no change on SRCS board
For the second year in a row, the typically routine task of electing school board members to leadership posts was a little less than routine for Sonoma County's largest school district. The Santa Rosa School Board on Wednesday night honored outgoing president Bill Carle with a heartfelt speech by Vice President Donna Jeye, followed by a gavel presentation. When Jeye finished, Carle thanked her for her "wonderful, kind words." "I feel like I died," he said. The meeting proceeded with… Read More »

subset: commoncrawl


text:
XEmacs / PROBLEMS
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
This file describes various problems that have been encountered
in compiling, installing and running XEmacs.
(synched up with: 19.30)
* On Irix, I don't see the toolbar icons and I'm getting lots of
entries in the warnings buffer.
SGI ships a really old Xpm library in /usr/lib which does not work at
all well with XEmacs. The solution is to install your own copy of the
latest version of Xpm somewhere and then use the --site-includes and
--site-libraries flags to tell configure where to find it.
* On Digital UNIX, the DEC C compiler might have a problem compiling
some files.
In particular, src/extents.c and src/faces.c might cause the DEC C
compiler to abort. When this happens: cd src, compile the files by
hand, cd .., and redo the "make" command. When recompiling the files by
hand, use the old C compiler for the following versions of Digital UNIX:
- V3.n: Remove "-migrate" from the compile command.
- V4.n: Add "-oldc" to the compile command.
* On HPUX, the HP C compiler might have a problem compiling some files
with optimization.
Richard Cognot <email@example.com> writes:
Had to drop once again to level 2 optimization, at least to
compile lstream.c. Otherwise, I get a "variable is void: \if"
problem while dumping (this is a problem I already reported
with vanilla hpux 10.01 and 9.07, which went away after
applying patches for the C compiler). Trouble is I still
haven't found the same patch for hpux 10.10, and I don't
remember the patch numbers. I think potential XEmacs builders
on HP should be warned about this.
* On HPUX, you get "poll: Interrupted system call" message in the window
where XEmacs was launched.
Richard Cognot <email@example.com> writes:
I get a very strange problem when linking libc.a
dynamically: every event (mouse, keyboard, expose...) results
in a "poll: Interrupted system call" message in the window
where XEmacs was launched. Forcing a static link of libc.a
alone by adding /usr/lib/libc.a at the end of the link line
solves this. Note that my 9.07 build of 19.14b17 and my (old)
build of 19.13 both exhibit the same behaviour. I've tried
various hpux patches to no avail. If this problem cannot be
solved before the release date, binary kits for HP *must* be
linked statically against libc, otherwise this problem will
show up. (This is directed at whoever will volunteer for this
kit, as I won't be available to do it, unless 19.14 gets
delayed until mid-june ;-). I think this problem will be an FAQ
soon after the release otherwise.
* Native cc on SCO OpenServer 5 is now OK. Icc may still throw you
a curve. Here is what Robert Lipe <email@example.com> says:
Unlike XEmacs 19.13, building with the native cc on SCO OpenServer 5
now produces a functional binary. I will typically build this
configuration for COFF with:
/path_to_XEmacs_source/configure --with-gcc=no \
--site-includes=/usr/local/include --site-libraries=/usr/local/lib \
--with-xpm --with-xface --with-sound=nas
This version now supports ELF builds. I highly recommend this to
reduce the in-core footprint of XEmacs. This is now how I compile
all my test releases. Build it like this:
/path_to_XEmacs_source/configure --with-gcc=no \
--site-includes=/usr/local/include --site-libraries=/usr/local/lib \
--with-xpm --with-xface --with-sound=nas --dynamic
The compiler known as icc [ supplied with the OpenServer 5 Development
System ] generates a working binary, but it takes forever to generate
XEmacs. ICC also whines more about the code than /bin/cc does. I do
believe all its whining is legitimate, however. Note that you do
have to 'cd src ; make LD=icc' to avoid linker errors.
The way I handle the build procedure is:
/path_to_XEmacs_source/configure --with-gcc=no \
--site-includes=/usr/local/include --site-libraries=/usr/local/lib \
--with-xpm --with-xface --with-sound=nas --dynamic --compiler="icc"
*NOTE* I have the xpm, xface, and audio libraries and includes in
/usr/local/lib, /usr/local/include. If you don't have these,
don't include the "--with-*" arguments in any of my examples.
In previous versions of XEmacs, you had to override the defaults while
compiling font-lock.o and extents.o when building with icc. This seems
to no longer be true, but I'm including this old information in case it
resurfaces. The process I used was:
make -k
[ procure pizza, beer, repeat ]
cd src
make CC="icc -W0,-mP1COPT_max_tree_size=3000" font-lock.o extents.o
make LD=icc
If you want sound support, get the tls566 supplement from
ftp.sco.com:/TLS or any of its mirrors. It works just groovy
with XEmacs.
The M-x manual-entry is known not to work. If you know Lisp and would
like help in making it work, e-mail me at <email@example.com>
In earlier releases, gnuserv/gnuclient/gnudoit would open a frame
just fine, but the client would lock up and the server would
terminate when you used C-x # to close the frame. This is now
fixed in XEmacs.
In etc/ there are two files of note. emacskeys.sco and emacsstrs.sco.
The comments at the top of emacskeys.sco describe its function, and
the emacstrs.sco is a suitable candidate for /usr/lib/keyboard/strings
to take advantage of the keyboard map in emacskeys.sco.
* Don't use -O2 with gcc under Linux without also using
-fno-strength-reduce. gcc will generate incorrect code otherwise.
This bug is present in at least 2.6.x and 2.7.[0-2]. A patched
binary for 2.7.2 is available in
Or wait for GCC 2.7.3.
* Under some versions of OSF XEmacs runs fine if built without
optimization but will crash randomly if built with optimization.
Using 'cc -g' is not sufficient to eliminate all optimization. Try
'cc -g -O0' instead.
* On HP/UX configure selects gcc even though it isn't actually present.
Some versions of SoftBench have an executable called 'gcc' that is not
actually the GNU C compiler. Use the --with-gcc=no flag when running
* When Emacs tries to ring the bell, you get an error like
audio: sst_open: SETQSIZE" Invalid argument
audio: sst_close: SETREG MMR2, Invalid argument
you have probably compiled using an ANSI C compiler, but with non-ANSI include
files. In particular, on Suns, the file /usr/include/sun/audioio.h uses the
_IOW macro to define the constant AUDIOSETQSIZE. _IOW in turn uses a K&R
preprocessor feature that is now explicitly forbidden in ANSI preprocessors,
namely substitution inside character constants. All ANSI C compilers must
provide a workaround for this problem. Lucid's C compiler is shipped with a
new set of system include files. If you are using GCC, there is a script
called fixincludes that creates new versions of some system include files that
use this obsolete feature.
* The `Alt' key doesn't behave as `Meta' when running DECwindows.
The default DEC keyboard mapping has the Alt keys set up to generate the
keysym `Multi_key', which has a meaning to xemacs which is distinct from that
of the `Meta_L' and `Meta-R' keysyms. A second problem is that certain keys
have the Mod2 modifier attached to them for no adequately explored reason.
The correct fix is to pass this file to xmodmap upon starting X:
clear mod2
keysym Multi_key = Alt_L
add mod1 = Alt_L
add mod1 = Alt_R
* I get complaints about the mapping of my HP keyboard at startup, but I
haven't changed anything.
The default HP keymap is set up to have Mod1 assigned to two different keys:
Meta_L and Mode_switch (even though there is not actually a Mode_switch key on
the keyboard -- it uses an "imaginary" keycode.) There actually is a reason
for this, but it's not a good one. The correct fix is to execute this command
upon starting X:
xmodmap -e 'remove mod1 = Mode_switch'
* I have focus problems when I use `M-o' to switch to another screen without
using the mouse.
The focus issues with a program like XEmacs, which has multiple homogeneous
top-level windows, are very complicated, and as a result, most window managers
don't implement them correctly.
The R4/R5 version of twm (and all of its descendants) had buggy focus
handling; there is a patch in .../xemacs/etc/twm-patch which fixes this.
Sufficiently recent versions of tvtwm do not need this patch, but most other
versions of twm do. If you need to apply this patch, please try to get it
integrated by the maintainer of whichever version of twm you're using.
In addition, if you're using twm, make sure you have not specified
"NoTitleFocus" in your .tvtwmrc file. The very nature of this option makes
twm do some illegal focus tricks, even with the patch.
It is known that olwm and olvwm are buggy, and in different ways. If you're
using click-to-type mode, try using point-to-type, or vice versa.
In older versions of NCDwm, one could not even type at XEmacs windows. This
has been fixed in newer versions (2.4.3, and possibly earlier).
(Many people suggest that XEmacs should warp the mouse when focusing on
another screen in point-to-type mode. This is not ICCCM-compliant behavior.
Implementing such policy is the responsibility of the window manager itself,
it is not legal for a client to do this.)
* My buffers are full of \000 characters or otherwise corrupt.
Some compilers have trouble with gmalloc.c and ralloc.c; try recompiling
without optimization. If that doesn't work, try recompiling with
SYSTEM_MALLOC defined, and/or with REL_ALLOC undefined.
* Some packages that worked before now cause the error
Wrong type argument: arrayp, #<face ... >
Code which uses the `face' accessor functions must be recompiled with xemacs
19.9 or later. The functions whose callers must be recompiled are: face-font,
face-foreground, face-background, face-background-pixmap, and face-underline-p.
The .elc files generated by version 19.9 will work in 19.6 and 19.8, but older
.elc files which contain calls to these functions will not work in 19.9.
* On Solaris 2.* I get undefined symbols from libcurses.a.
You probably have /usr/ucblib/ on your LD_LIBRARY_PATH. Do the link with
LD_LIBRARY_PATH unset.
* I don't have `xmkmf' and `imake' on my HP.
You can get these standard X tools by anonymous FTP to hpcvaaz.cv.hp.com.
Essentially all X programs need these.
* When emacs starts up, I get lots of warnings about unknown keysyms.
If you are running the prebuilt binaries, the Motif library expects to find
certain thing in the XKeysymDB file. This file is normally in /usr/lib/X11/
or in /usr/openwin/lib/. If you keep yours in a different place, set the
environment variable $XKEYSYMDB to point to it before starting emacs. If
you still have the problem after doing that, perhaps your version of X is
too old. There is a copy of the MIT X11R5 XKeysymDB file in the emacs `etc'
directory. Try using that one.
* My X resources used to work, and now some of them are being ignored.
Check the resources in .../etc/Emacs.ad (which is the same as the file
sample.Xdefaults). Perhaps some of the default resources built in to
emacs are now overriding your existing resources. Copy and edit the
resources in Emacs.ad as necessary.
* Solaris 2.3 /bin/sh coredumps during configuration.
This only occurs if you have LANG != C. This is a known bug with
/bin/sh fixed by installing Patch-ID# 101613-01.
* "Cannot find callback list" messages from dialog boxes on HPUX, in
Emacs built with Motif.
This problem resulted from a bug in GCC 2.4.5. Newer GCC versions
such as 2.7.0 fix the problem.
* On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
A compiler bug inserts spaces into the string "unexelfsgi . o"
in src/Makefile. Edit src/Makefile, after configure is run,
find that string, and take out the spaces.
Compiler fixes in Irix 6.0.1 should eliminate this problem.
* With certain fonts, when the cursor appears on a character, the
character doesn't appear--you get a solid box instead.
One user on a Linux-based GNU system reported that this problem went
away with installation of a new X server. The failing server was
XFree86 3.1.1. XFree86 3.1.2 works.
* On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
This happens if you configure Emacs specifying just `sparc-sun-sunos4'
on a system that is version 4.1.3. You must specify the precise
version number (or let configure figure out the configuration, which
it can do perfectly well for SunOS).
* On SunOS 4, Emacs processes keep going after you kill the X server
(or log out, if you logged in using X).
Someone reported that recompiling with GCC 2.7.0 fixed this problem.
* On AIX 4, some programs fail when run in a Shell buffer
with an error message like No terminfo entry for "unknown".
On AIX, many terminal type definitions are not installed by default.
`unknown' is one of them. Install the "Special Generic Terminal
Definitions" to make them defined.
* On SunOS, you get linker errors
ld: Undefined symbol
The fix to this is to install patch 100573 for OpenWindows 3.0
or link libXmu statically.
* On AIX 4.1.2, linker error messages such as
ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
This is a problem in libIM.a. You can work around it by executing
these shell commands in the src subdirectory of the directory where
you build Emacs:
cp /usr/lib/libIM.a .
chmod 664 libIM.a
ranlib libIM.a
Then change -lIM to ./libIM.a in the command to link temacs (in
* Unpredictable segmentation faults on Solaris 2.3 and 2.4.
A user reported that this happened in 19.29 when it was compiled with
the Sun compiler, but not when he recompiled with GCC 2.7.0.
We do not know whether something in Emacs is partly to blame for this.
* Emacs exits with "X protocol error" when run with an X server for
A certain X server for Windows had a bug which caused this.
Supposedly the newer 32-bit version of this server doesn't have the
* A position you specified in .Xdefaults is ignored, using twm.
twm normally ignores "program-specified" positions.
You can tell it to obey them with this command in your `.twmrc' file:
UsePPosition "on" #allow clents to request a position
* Compiling lib-src says there is no rule to make test-distrib.c.
This results from a bug in a VERY old version of GNU Sed. To solve
the problem, install the current version of GNU Sed, then rerun
Emacs's configure script.
* On Sunos 4.1.1, there are errors compiling sysdep.c.
If you get errors such as
"sysdep.c", line 2017: undefined structure or union
"sysdep.c", line 2017: undefined structure or union
"sysdep.c", line 2019: nodename undefined
This can result from defining LD_LIBRARY_PATH. It is very tricky
to use that environment variable with Emacs. The Emacs configure
script links many test programs with the system libraries; you must
make sure that the libraries available to configure are the same
ones available when you build Emacs.
* The right Alt key works wrong on German HP keyboards (and perhaps
other non-English HP keyboards too).
This is because HPUX defines the modifiers wrong in X. Here is a
shell script to fix the problem; be sure that it is run after VUE
configures the X server.
xmodmap 2> /dev/null - << EOF
keysym Alt_L = Meta_L
keysym Alt_R = Meta_R
xmodmap - << EOF
clear mod1
keysym Mode_switch = NoSymbol
add mod1 = Meta_L
keysym Meta_R = Mode_switch
add mod2 = Mode_switch
* The Emacs window disappears when you type M-q.
Some versions of the Open Look window manager interpret M-q as a quit
command for whatever window you are typing at. If you want to use
Emacs with that window manager, you should try to configure the window
manager to use some other command. You can disable the
shortcut keys entirely by adding this line to ~/.OWdefaults:
OpenWindows.WindowMenuAccelerators: False
* Emacs does not notice when you release the mouse.
There are reports that this happened with (some) Microsoft mice and
that replacing the mouse made it stop.
* Trouble using ptys on IRIX, or running out of ptys.
The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
be set-UID to root, or non-root programs like Emacs will not be able
to allocate ptys reliably.
* On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
The file cmplrs/stsupport.h was included in the wrong file set in the
Irix 5.2 distribution. You can find it in the optional fileset
compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
workaround is to change unexelfsgi.c to include sym.h instead of
* Slow startup on Linux.
People using systems based on the Linux kernel sometimes report that
startup takes 10 to 15 seconds longer than `usual'.
This is because Emacs looks up the host name when it starts.
Normally, this takes negligible time; the extra delay is due to
improper system configuration. This problem can occur for both
networked and non-networked machines.
Here is how to fix the configuration. It requires being root.
** Networked Case
First, make sure the files `/etc/hosts' and `/etc/host.conf' both
exist. The first line in the `/etc/hosts' file should look like this
(replace HOSTNAME with your host name):
Also make sure that the `/etc/host.conf' files contains the following
order hosts, bind
multi on
Any changes, permanent and temporary, to the host name should be
indicated in the `/etc/hosts' file, since it acts a limited local
database of addresses and names (e.g., some SLIP connections
dynamically allocate ip addresses).
** Non-Networked Case
The solution described in the networked case applies here as well.
However, if you never intend to network your machine, you can use a
simpler solution: create an empty `/etc/host.conf' file. The command
`touch /etc/host.conf' suffices to create the file. The `/etc/hosts'
file is not necessary with this approach.
* On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs
forever waiting for termination of a subprocess that is a zombie.
email@example.com says the problem is in X11R6. Rebuild libX11.so
after changing the file xc/config/cf/sunLib.tmpl. Change the lines
#if ThreadedX
#define SharedX11Reqs -lthread
#if OSMinorVersion < 4
#if ThreadedX
#define SharedX11Reqs -lthread
Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
(as it should be for Solaris 2.4). The file has three definitions for
OSMinorVersion: the first is for x86, the second for SPARC under
Solaris, and the third for SunOS 4. Make sure to update the
definition for your type of machine and system.
Then do `make Everything' in the top directory of X11R6, to rebuild
the makefiles and rebuild X. The X built this way work only on
Solaris 2.4, not on 2.3.
For multithreaded X to work it necessary to install patch
101925-02 to fix problems in header files [2.4]. You need
to reinstall gcc or re-run just-fixinc after installing that
However, Frank Rust <email@example.com> used a simpler solution:
he changed
#define ThreadedX YES
#define ThreadedX NO
in sun.cf and did `make World' to rebuild X11R6. Removing all
`-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
typing 'make install' in that directory also seemed to work.
* With M-x enable-flow-control, you need to type C-\ twice
to do incremental search--a single C-\ gets no response.
This has been traced to communicating with your machine via kermit,
with C-\ as the kermit escape character. One solution is to use
another escape character in kermit. One user did
set escape-character 17
in his .kermrc file, to make C-q the kermit escape character.
* The Motif version of Emacs paints the screen a solid color.
This has been observed to result from the following X resource:
Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
That the resource has this effect indicates a bug in something, but we
do not yet know what. If it is an Emacs bug, we hope someone can
explain what the bug is so we can fix it. In the mean time, removing
the resource prevents the problem.
* Emacs gets hung shortly after startup, on Sunos 4.1.3.
We think this is due to a bug in Sunos. The word is that
one of these Sunos patches fixes the bug:
100075-11 100224-06 100347-03 100482-05 100557-02 100623-03 100804-03 101080-01
100103-12 100249-09 100496-02 100564-07 100630-02 100891-10 101134-01
100170-09 100296-04 100377-09 100507-04 100567-04 100650-02 101070-01 101145-01
100173-10 100305-15 100383-06 100513-04 100570-05 100689-01 101071-03 101200-02
100178-09 100338-05 100421-03 100536-02 100584-05 100784-01 101072-01 101207-01
We don't know which of these patches really matter. If you find out
which ones, please inform firstname.lastname@example.com.
* Emacs aborts while starting up, only when run without X.
This problem often results from compiling Emacs with GCC when GCC was
installed incorrectly. The usual error in installing GCC is to
specify --includedir=/usr/include. Installation of GCC makes
corrected copies of the system header files. GCC is supposed to use
the corrected copies in preference to the original system headers.
Specifying --includedir=/usr/include causes the original system header
files to be used. On some systems, the definition of ioctl in the
original system header files is invalid for ANSI C and causes Emacs
not to work.
The fix is to reinstall GCC, and this time do not specify --includedir
when you configure it. Then recompile Emacs. Specifying --includedir
is appropriate only in very special cases and it should *never* be the
same directory where system header files are kept.
* The Compose key on a DEC keyboard does not work as Meta key.
This shell command should fix it:
xmodmap -e 'keycode 0xb1 = Meta_L'
* Regular expressions matching bugs on SCO systems.
On SCO, there are problems in regexp matching when Emacs is compiled
with the system compiler. The compiler version is "Microsoft C
version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
C Compiler Version 1.00.46 (Beta). The solution is to compile with
* On Sunos 4, you get the error ld: Undefined symbol __lib_version.
This is the result of using cc or gcc with the shared library meant
for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete
/usr/lang/SC2.0.1 or some similar directory.
* You can't select from submenus.
On certain systems, mouse-tracking and selection in top-level menus
works properly with the X toolkit, but neither of them works when you
bring up a submenu (such as Bookmarks or Compare or Apply Patch, in
the Files menu).
This works on most systems. There is speculation that the failure is
due to bugs in old versions of X toolkit libraries, but no one really
knows. If someone debugs this and finds the precise cause, perhaps a
workaround can be found.
* Unusable default font on SCO 3.2v4.
The Open Desktop environment comes with default X resource settings
that tell Emacs to use a variable-width font. Emacs cannot use such
fonts, so it does not work.
This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
the application-specific resource file for the `scoterm' terminal
emulator program. It contains several extremely general X resources
that affect other programs besides `scoterm'. In particular, these
resources affect Emacs also:
*Font: -*-helvetica-medium-r-*--12-*-p-*
*Background: scoBackground
*Foreground: scoForeground
The best solution is to create an application-specific resource file for
Emacs, /usr/lib/X11/app-defaults/Emacs, with the following contents:
Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
Emacs*Background: white
Emacs*Foreground: black
(or whatever other defaults you prefer).
These resource files are not normally shared across a network of SCO
machines; you must create the file on each machine individually.
* rcs2log gives you the awk error message "too many fields".
This is due to an arbitrary limit in certain versions of awk.
The solution is to use gawk (GNU awk).
* Emacs is slow using X11R5 on HP/UX.
This happens if you use the MIT versions of the X libraries--it
doesn't run as fast as HP's version. People sometimes use the version
because they see the HP version doesn't have the libraries libXaw.a,
libXmu.a, libXext.a and others. HP/UX normally doesn't come with
those libraries installed. To get good performance, you need to
install them and rebuild Emacs.
* Loading fonts is very slow.
You might be getting scalable fonts instead of precomputed bitmaps.
Known scalable font directories are "Type1" and "Speedo". A font
directory contains scalable fonts if it contains the file
If this is so, re-order your X windows font path to put the scalable
font directories last. See the documentatoin of `xset' for details.
With some X servers, it may be necessary to take the scalable font
directories out of your path entirely, at least for Emacs 19.26.
Changes in the future may make this unnecessary.
* On AIX 3.2.4, releasing Ctrl/Act key has no effect, if Shift is down.
Due to a feature of AIX, pressing or releasing the Ctrl/Act key is
ignored when the Shift, Alt or AltGr keys are held down. This can
lead to the keyboard being "control-locked"--ordinary letters are
treated as control characters.
You can get out of this "control-locked" state by pressing and
releasing Ctrl/Act while not pressing or holding any other keys.
* display-time causes kernel problems on ISC systems.
Under Interactive Unix versions 3.0.1 and 4.0 (and probably other
versions), display-time causes the loss of large numbers of STREVENT
cells. Eventually the kernel's supply of these cells is exhausted.
This makes emacs and the whole system run slow, and can make other
processes die, in particular pcnfsd.
Other emacs functions that communicate with remote processes may have
the same problem. Display-time seems to be far the worst.
The only known fix: Don't run display-time.
* On Solaris, C-x doesn't get through to Emacs when you use the console.
This is a Solaris feature (at least on Intel x86 cpus). Type C-r
C-r C-t, to toggle whether C-x gets through to Emacs.
* Error message `Symbol's value as variable is void: x', followed by
segmentation fault and core dump.
This has been tracked to a bug in tar! People report that tar erroneously
added a line like this at the beginning of files of Lisp code:
x FILENAME, N bytes, B tape blocks
If your tar has this problem, install GNU tar--if you can manage to
untar it :-).
* Link failure when using acc on a Sun.
To use acc, you need additional options just before the libraries, such as
/usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
and you need to add -lansi just before -lc.
The precise file names depend on the compiler version, so we
cannot easily arrange to supply them.
* Link failure on IBM AIX 1.3 ptf 0013.
There is a real duplicate definition of the function `_slibc_free' in
the library /lib/libc_s.a (just do nm on it to verify). The
workaround/fix is:
cd /lib
ar xv libc_s.a NLtmtime.o
ar dv libc_s.a NLtmtime.o
* Undefined symbols _dlopen, _dlsym and/or _dlclose on a Sun.
If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking
with -lX11, compile and link against the file mit/util/misc/dlsym.c in
the MIT X11R5 distribution. Alternatively, link temacs using shared
libraries with s/sunos4shr.h. (This doesn't work if you use the X
If you get the additional error that the linker could not find
lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in
X11R4, then use it in the link.
* In Shell mode, you get a ^M at the end of every line.
This happens to people who use tcsh, because it is trying to be too
smart. It sees that the Shell uses terminal type `unknown' and turns
on the flag to output ^M at the end of each line. You can fix the
problem by adding this to your .cshrc file:
if ($?EMACS) then
if ($EMACS == "t") then
unset edit
stty -icrnl -onlcr -echo susp ^Z
* An error message such as `X protocol error: BadMatch (invalid
parameter attributes) on protocol request 93'.
This comes from having an invalid X resource, such as
emacs*Cursor: black
(which is invalid because it specifies a color name for something
that isn't a color.)
The fix is to correct your X resources.
* Undefined symbols when linking on Sunos 4.1.
If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
_iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
-lXaw in the command that links temacs.
This problem seems to arise only when the international language
extensions to X11R5 are installed.
* Typing C-c C-c in Shell mode kills your X server.
This happens with Linux kernel 1.0 thru 1.04, approximately. The workaround is
to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs.
Newer Linux kernel versions don't have this problem.
* src/Makefile and lib-src/Makefile are truncated--most of the file missing.
This can happen if configure uses GNU sed version 2.03. That version
had a bug. GNU sed version 2.05 works properly.
* Slow startup on X11R6 with X windows.
If Emacs takes two minutes to start up on X11R6, see if your X
resources specify any Adobe fonts. That causes the type-1 font
renderer to start up, even if the font you asked for is not a type-1
One way to avoid this problem is to eliminate the type-1 fonts from
your font path, like this:
xset -fp /usr/X11R6/lib/X11/fonts/Type1/
* Pull-down menus appear in the wrong place, in the toolkit version of Emacs.
An X resource of this form can cause the problem:
Emacs*geometry: 80x55+0+0
This resource is supposed to apply, and does apply, to the menus
individually as well as to Emacs frames. If that is not what you
want, rewrite the resource.
To check thoroughly for such resource specifications, use `xrdb
-query' to see what resources the X server records, and also look at
the user's ~/.Xdefaults and ~/.Xdefaults-* files.
* `make install' fails on install-doc with `Error 141'.
This happens on Ultrix 4.2 due to failure of a pipeline of tar
commands. We don't know why they fail, but the bug seems not to be in
Emacs. The workaround is to run the shell command in install-doc by
* Subprocesses remain, hanging but not zombies, on Sunos 5.3.
A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
exits. Sun patch # 101415-02 is part of the fix for this, but it only
applies to ptys, and doesn't fix the problem with subprocesses
communicating through pipes.
* Mail is lost when sent to local aliases.
Many emacs mail user agents (VM and rmail, for instance) use the
sendmail.el library. This library can arrange for mail to be
delivered by passing messages to the /usr/lib/sendmail (usually)
program . In doing so, it passes the '-t' flag to sendmail, which
means that the name of the recipient of the message is not on the
command line and, therefore, that sendmail must parse the message to
obtain the destination address.
There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
In short, when given the -t flag, the SunOS sendmail won't recognize
non-local (i.e. NIS) aliases. It has been reported that the Solaris
2.x versions of sendmail do not have this bug. For those using SunOS
4.1, the best fix is to install sendmail V8 or IDA sendmail (which
have other advantages over the regular sendmail as well). At the time
of this writing, these official versions are available:
Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
sendmail.8.6.9.base.tar.Z (the base system source & documentation)
sendmail.8.6.9.cf.tar.Z (configuration files)
sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
IDA sendmail on vixen.cso.uiuc.edu in /pub:
* On AIX, you get this message when running Emacs:
Could not load program emacs
Symbol smtcheckinit in csh is undefined
Error was: Exec format error
or this one:
Could not load program .emacs
Symbol _system_con in csh is undefined
Symbol _fp_trapsta in csh is undefined
Error was: Exec format error
These can happen when you try to run on AIX 3.2.5 a program that was
compiled with 3.2.4. The fix is to recompile.
* On AIX, you get this compiler error message:
Processing include file ./XMenuInt.h
1501-106: (S) Include file X11/Xlib.h not found.
This means your system was installed with only the X11 runtime i.d
libraries. You have to find your sipo (bootable tape) and install
X11Dev... with smit.
* You "lose characters" after typing Compose Character key.
This is because the Compose Character key is defined as the keysym
Multi_key, and Emacs (seeing that) does the proper X11
character-composition processing. If you don't want your Compose key
to do that, you can redefine it with xmodmap.
For example, here's one way to turn it into a Meta key:
xmodmap -e "keysym Multi_key = Meta_L"
If all users at your site of a particular keyboard prefer Meta to
Compose, you can make the remapping happen automatically by adding the
xmodmap command to the xdm setup script for that display.
* C-z just refreshes the screen instead of suspending Emacs.
You are probably using a shell that doesn't support job control, even
though the system itself is capable of it. Either use a different shell,
or set the variable `cannot-suspend' to a non-nil value.
* Watch out for .emacs files and EMACSLOADPATH environment vars
These control the actions of Emacs.
~/.emacs is your Emacs init file.
EMACSLOADPATH overrides which directories the function
"load" will search.
If you observe strange problems, check for these and get rid
of them, then try again.
* After running emacs once, subsequent invocations crash.
Some versions of SVR4 have a serious bug in the implementation of the
mmap () system call in the kernel; this causes emacs to run correctly
the first time, and then crash when run a second time.
Contact your vendor and ask for the mmap bug fix; in the mean time,
you may be able to work around the problem by adding a line to your
operating system description file (whose name is reported by the
configure script) that reads:
#define SYSTEM_MALLOC
This makes Emacs use memory less efficiently, but seems to work around
the kernel bug.
* Inability to send an Alt-modified key, when Emacs is communicating
directly with an X server.
If you have tried to bind an Alt-modified key as a command, and it
does not work to type the command, the first thing you should check is
whether the key is getting through to Emacs. To do this, type C-h c
followed by the Alt-modified key. C-h c should say what kind of event
it read. If it says it read an Alt-modified key, then make sure you
have made the key binding correctly.
If C-h c reports an event that doesn't have the Alt modifier, it may
be because your X server has no key for the Alt modifier. The X
server that comes from MIT does not set up the Alt modifier by
If your keyboard has keys named Alt, you can enable them as follows:
xmodmap -e 'add mod2 = Alt_L'
xmodmap -e 'add mod2 = Alt_R'
If the keyboard has just one key named Alt, then only one of those
commands is needed. The modifier `mod2' is a reasonable choice if you
are using an unmodified MIT version of X. Otherwise, choose any
modifier bit not otherwise used.
If your keyboard does not have keys named Alt, you can use some other
keys. Use the keysym command in xmodmap to turn a function key (or
some other 'spare' key) into Alt_L or into Alt_R, and then use the
commands show above to make them modifier keys.
Note that if you have Alt keys but no Meta keys, Emacs translates Alt
into Meta. This is because of the great importance of Meta in Emacs.
* `Pid xxx killed due to text modification or page I/O error'
On HP/UX, you can get that error when the Emacs executable is on an NFS
file system. HP/UX responds this way if it tries to swap in a page and
does not get a response from the server within a timeout whose default
value is just ten seconds.
If this happens to you, extend the timeout period.
* `expand-file-name' fails to work on any but the machine you dumped Emacs on.
On Ultrix, if you use any of the functions which look up information
in the passwd database before dumping Emacs (say, by using
expand-file-name in site-init.el), then those functions will not work
in the dumped Emacs on any host but the one Emacs was dumped on.
The solution? Don't use expand-file-name in site-init.el, or in
anything it loads. Yuck - some solution.
I'm not sure why this happens; if you can find out exactly what is
going on, and perhaps find a fix or a workaround, please let us know.
Perhaps the YP functions cache some information, the cache is included
in the dumped Emacs, and is then inaccurate on any other host.
* On some variants of SVR4, Emacs does not work at all with X.
Try defining BROKEN_FIONREAD in your config.h file. If this solves
the problem, please send a bug report to tell us this is needed; be
sure to say exactly what type of machine and system you are using.
* Emacs fails to understand most Internet host names, even though
the names work properly with other programs on the same system.
* Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
* GNUs can't make contact with the specified host for nntp.
This typically happens on Suns and other systems that use shared
libraries. The cause is that the site has installed a version of the
shared library which uses a name server--but has not installed a
similar version of the unshared library which Emacs uses.
The result is that most programs, using the shared library, work with
the nameserver, but Emacs does not.
The fix is to install an unshared library that corresponds to what you
installed in the shared library, and then relink Emacs.
On SunOS 4.1, simply define HAVE_RES_INIT.
If you have already installed the name resolver in the file libresolv.a,
then you need to compile Emacs to use that library. The easiest way to
do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro
that is already in use in your configuration to supply some other libraries,
be careful not to lose the others.
Thus, you could start by adding this to config.h:
#define LIBS_SYSTEM -lresolv
Then if this gives you an error for redefining a macro, and you see that
the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
again to say this:
#define LIBS_SYSTEM -lresolv -lfoo -lbar
* On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
/lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
The problem is in the Sun shared C library, not in GNU ld.
The solution is to install Patch-ID# 100267-03 from Sun.
* SunOS 4.1.2: undefined symbol _get_wmShellWidgetClass
Apparently the version of libXmu.so.a that Sun ships is hosed: it's missing
some stuff that is in libXmu.a (the static version). Sun has a patch for
this, but a workaround is to use the static version of libXmu, by changing
the link command from "-lXmu" to "-Bstatic -lXmu -Bdynamic". If you have
OpenWindows 3.0, ask Sun for these patches:
100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
100573-03 4.1.x OpenWindows 3.0 undefined symbols with shared libXmu
* Random other SunOS 4.1.[12] link errors.
The X headers and libraries that Sun ships in /usr/{include,lib}/X11 are
broken. Use the ones in /usr/openwin/{include,lib} instead.
* Bus errors on startup when compiled with Sun's "acc" (in the routine
make_string_internal() called from initialize_environment_alist())
The Sun ANSI compiler doesn't place uninitialized static variables in BSS
space like other compilers do. This breaks emacs. If you want to use acc,
you need to make the file "lastfile.o" be the *first* file in the link
command. Better yet, use Lucid C or GCC.
* The compiler generates lots and lots of syntax errors.
Are you using an ANSI C compiler, like lcc or gcc? The SunOS 4.1 bundled cc
is not ANSI.
If X has not been configured to compile itself using lcc, gcc, or another ANSI
compiler, then you will have to hack the automatically-generated makefile in
the `lwlib' directory by hand to make it use an ANSI compiler.
* When using gcc, you get the error message "undefined symbol __fixunsdfsi".
* When using gcc, you get the error message "undefined symbol __main".
This means that you need to link with the gcc library. It may be called
"gcc-gnulib" or "libgcc.a"; figure out where it is, and define LIB_GCC in
config.h to point to it.
It may also work to use the GCC version of `ld' instead of the standard one.
* When compiling with X11, you get "undefined symbol _XtStrings".
This means that you are trying to link emacs against the X11r4 version of
libXt.a, but you have compiled either Emacs or the code in the lwlib
subdirectory with the X11r5 header files. That doesn't work.
Remember, you can't compile lwlib for r4 and emacs for r5, or vice versa.
They must be in sync.
* Self documentation messages are garbled.
This means that the file `etc/DOC-...' doesn't properly correspond
with the Emacs executable. Redumping Emacs and then installing the
corresponding pair of files should fix the problem.
* Trouble using ptys on AIX.
People often install the pty devices on AIX incorrectly.
Use `smit pty' to reinstall them properly.
* Shell mode on HP/UX gives the message, "`tty`: Ambiguous".
email@example.com says:
The problem is that in your .cshrc you have something that tries to
execute `tty`. If you are not running the shell on a real tty then
tty will print "not a tty". Csh expects one word in some places,
but tty is giving it back 3.
The solution is to add a pair of quotes around `tty` to make it a single
if (`tty` == "/dev/console")
should be changed to:
if ("`tty`" == "/dev/console")
Even better, move things that set up terminal sections out of .cshrc
and into .login.
* With process-connection-type set to t, each line of subprocess output is
terminated with a ^M, making ange-ftp and GNUS not work.
On SunOS systems, this problem has been seen to be a result of an incomplete
installation of gcc 2.2 which allowed some non-ANSI compatible include files
into the compilation. In particular this affected virtually all ioctl() calls.
* Once you pull down a menu from the menubar, it won't go away.
It has been claimed that this is caused by a bug in certain very old (1990?)
versions of the twm window manager. It doesn't happen with recent vintages,
or with other window managers.
* Emacs ignores the "help" key when running OLWM.
OLWM grabs the help key, and retransmits it to the appropriate client using
XSendEvent. Allowing emacs to react to synthetic events is a security hole,
so this is turned off by default. You can enable it by setting the variable
x-allow-sendevents to t. You can also cause fix this by telling OLWM to not
grab the help key, with the null binding "OpenWindows.KeyboardCommand.Help:".
* Something awful happens when I type M-ESC, instead of `eval-expression'.
MWM intercepts this and several other keys. Turn this off by adding this to
your resources: "mwm*keyBindings: NoKeyBindings".
* Using X Windows, control-shift-leftbutton makes Emacs hang.
Use the shell command `xset bc' to make the old X Menu package work.
* Emacs running under X Windows does not handle mouse clicks.
* `emacs -geometry 80x20' finds a file named `80x20'.
One cause of such problems is having (setq term-file-prefix nil) in
your .emacs file. Another cause is a bad value of EMACSLOADPATH in
the environment.
* Emacs gets error message from linker on Sun.
If the error message says that a symbol such as `f68881_used' or
`ffpa_used' or `start_float' is undefined, this probably indicates
that you have compiled some libraries, such as the X libraries,
with a floating point option other than the default.
It's not terribly hard to make this work with small changes in
crt0.c together with linking with Fcrt1.o, Wcrt1.o or Mcrt1.o.
However, the easiest approach is to build Xlib with the default
floating point option: -fsoft to decide at run time what hardware
is available.
* Keyboard input gets confused after a beep when using a DECserver
as a concentrator.
This problem seems to be a matter of configuring the DECserver to use
7 bit characters rather than 8 bit characters.
* M-x shell persistently reports "Process shell exited abnormally with code 1".
This happened on Suns as a result of what is said to be a bug in Sunos
version 4.0.x. The only fix was to reboot the machine.
* Programs running under terminal emulator do not recognize `emacs'
terminal type.
The cause of this is a shell startup file that sets the TERMCAP
environment variable. The terminal emulator uses that variable to
provide the information on the special terminal type that Emacs
Rewrite your shell startup file so that it does not change TERMCAP
in such a case. You could use the following conditional which sets
it only if it is undefined.
if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
Or you could set TERMCAP only when you set TERM--which should not
happen in a non-login shell.
* Problem with remote X server on Suns.
On a Sun, running Emacs on one machine with the X server on another
may not work if you have used the unshared system libraries. This
is because the unshared libraries fail to use YP for host name lookup.
As a result, the host name you specify may not be recognized.
* Shell mode ignores interrupts on Apollo Domain
You may find that M-x shell prints the following message:
Warning: no access to tty; thus no job control in this shell...
This can happen if there are not enough ptys on your system.
Here is how to make more of them.
% cd /dev
% ls pty*
# shows how many pty's you have. I had 8, named pty0 to pty7)
% /etc/crpty 8
# creates eight new pty's
* Fatal signal in the command temacs -l loadup inc dump
This command is the final stage of building Emacs. It is run by the
Makefile in the src subdirectory, or by build.com on VMS.
It has been known to get fatal errors due to insufficient swapping
space available on the machine.
On 68000's, it has also happened because of bugs in the
subroutine `alloca'. Verify that `alloca' works right, even
for large blocks (many pages).
* test-distrib says that the distribution has been clobbered
* or, temacs prints "Command key out of range 0-127"
* or, temacs runs and dumps xemacs, but xemacs totally fails to work.
* or, temacs gets errors dumping xemacs
This can be because the .elc files have been garbled. Do not be
fooled by the fact that most of a .elc file is text: these are
binary files and can contain all 256 byte values.
In particular `shar' cannot be used for transmitting GNU Emacs.
It typically truncates "lines". What appear to be "lines" in
a binary file can of course be of any length. Even once `shar'
itself is made to work correctly, `sh' discards null characters
when unpacking the shell archive.
I have also seen character \177 changed into \377. I do not know
what transfer means caused this problem. Various network
file transfer programs are suspected of clobbering the high bit.
If you have a copy of Emacs that has been damaged in its
nonprinting characters, you can fix them:
1) Record the names of all the .elc files.
2) Delete all the .elc files.
3) Recompile alloc.c with a value of PURESIZE twice as large.
You might as well save the old alloc.o.
4) Remake xemacs. It should work now.
5) Running xemacs, do Meta-x byte-compile-file repeatedly
to recreate all the .elc files that used to exist.
You may need to increase the value of the variable
max-lisp-eval-depth to succeed in running the compiler interpreted
on certain .el files. 400 was sufficient as of last report.
6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
and remake temacs.
7) Remake xemacs. It should work now, with valid .elc files.
* temacs prints "Pure Lisp storage exhausted"
This means that the Lisp code loaded from the .elc and .el
files during temacs -l loadup inc dump took up more
space than was allocated.
This could be caused by
1) adding code to the preloaded Lisp files
2) adding more preloaded files in loadup.el
3) having a site-init.el or site-load.el which loads files.
Note that ANY site-init.el or site-load.el is nonstandard;
if you have received Emacs from some other site
and it contains a site-init.el or site-load.el file, consider
deleting that file.
4) getting the wrong .el or .elc files
(not from the directory you expected).
5) deleting some .elc files that are supposed to exist.
This would cause the source files (.el files) to be
loaded instead. They take up more room, so you lose.
6) a bug in the Emacs distribution which underestimates
the space required.
If the need for more space is legitimate, use the --puresize option
to `configure' to specify more pure space.
But in some of the cases listed above, this problem is a consequence
of something else that is wrong. Be sure to check and fix the real
* Changes made to .el files do not take effect.
You may have forgotten to recompile them into .elc files.
Then the old .elc files will be loaded, and your changes
will not be seen. To fix this, do M-x byte-recompile-directory
and specify the directory that contains the Lisp files.
Note that you may get a warning when loading a .elc file that
is older than the corresponding .el file.
* Things which should be bold or italic (such as the initial copyright notice)
are not.
The fonts of the "bold" and "italic" faces are generated from the font of
the "default" face; in this way, your bold and italic fonts will have the
appropriate size and family. However, emacs can only be clever in this
way if you have specified the default font using the XLFD (X Logical Font
Description) format, which looks like
if you use any of the other, less strict font name formats, some of which
look like
and fixed
and 9x13
then emacs won't be able to guess the names of the "bold" and "italic"
versions. All X fonts can be referred to via XLFD-style names, so you
should use those forms. See the man pages for X(1), xlsfonts(1), and
* The dumped Emacs (xemacs) crashes when run, trying to write pure data.
Two causes have been seen for such problems.
1) On a system where getpagesize is not a system call, it is defined
as a macro. If the definition (in both unexec.c and malloc.c) is wrong,
it can cause problems like this. You might be able to find the correct
value in the man page for a.out (5).
2) Some systems allocate variables declared static among the
initialized variables. Emacs makes all initialized variables in most
of its files pure after dumping, but the variables declared static and
not initialized are not supposed to be pure. On these systems you
may need to add "#define static" to the m- or the s- file.
* Reading and writing files is very very slow.
Try evaluating the form (setq lock-directory nil) and see if that helps.
There is a problem with file-locking on some systems (possibly related
to NFS) that I don't understand. Please send mail to the address
email@example.com if you figure this one out.
* Compilation errors on VMS.
Sorry, XEmacs does not work under VMS. You might consider working on
the port if you really want to have XEmacs work under VMS.
* "Symbol's value as variable is void: unread-command-char".
* "Wrong type argument: arrayp, #<keymap 143 entries>"
* "Wrong type argument: stringp, [#<keypress-event return>]"
There are a few incompatible changes in XEmacs, and these are the
symptoms. Some of the emacs-lisp code you are running needs to be
updated to be compatible with XEmacs.
We have provided modified versions of several popular emacs packages (GNUS,
VM, etc) which are compatible with this version of emacs. Check to make
sure you have not set your load-path so that your private copies of these
packages are being found before the versions in the lisp directory.
Make sure that your load-path and your $EMACSLOADPATH environment variable
are not pointing at an Emacs18 lisp directory. This will cripple emacs.
* rmail or VM gets error getting new mail
rmail and VM get new mail from /usr/spool/mail/$USER using a program
called `movemail'. This program interlocks with /bin/mail using
the protocol defined by /bin/mail.
There are two different protocols in general use. One of them uses
the `flock' system call. The other involves creating a lock file;
`movemail' must be able to write in /usr/spool/mail in order to do
this. You control which one is used by defining, or not defining,
the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes.
If your system uses the lock file protocol, and fascist restrictions
prevent ordinary users from writing the lock files in /usr/spool/mail,
you may need to make `movemail' setgid to a suitable group such as
`mail'. You can use these commands (as root):
chgrp mail movemail
chmod 2755 movemail
If your system uses the lock file protocol, and fascist restrictions
prevent ordinary users from writing the lock files in /usr/spool/mail,
you may need to make `movemail' setgid to a suitable group such as
`mail'. To do this, use the following commands (as root) after doing the
make install.
chgrp mail movemail
chmod 2755 movemail
Installation normally copies movemail from the build directory to an
installation directory which is usually under /usr/local/lib. The
installed copy of movemail is usually in the directory
/usr/local/lib/emacs/VERSION/TARGET. You must change the group and
mode of the installed copy; changing the group and mode of the build
directory copy is ineffective.
* Emacs spontaneously displays "I-search: " at the bottom of the screen.
This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
used. C-s/C-q flow control is bad for Emacs editors because it takes
away C-s and C-q as user commands. Since editors do not output long
streams of text without user commands, there is no need for a
user-issuable "stop output" command in an editor; therefore, a
properly designed flow control mechanism would transmit all possible
input characters without interference. Designing such a mechanism is
easy, for a person with at least half a brain.
There are three possible reasons why flow control could be taking place:
1) Terminal has not been told to disable flow control
2) Insufficient padding for the terminal in use
3) Some sort of terminal concentrator or line switch is responsible
First of all, many terminals have a set-up mode which controls whether
they generate XON/XOFF flow control characters. This must be set to
"no XON/XOFF" in order for Emacs to work. Sometimes there is an
escape sequence that the computer can send to turn flow control off
and on. If so, perhaps the termcap `ti' string should turn flow
control off, and the `te' string should turn it on.
Once the terminal has been told "no flow control", you may find it
needs more padding. The amount of padding Emacs sends is controlled
by the termcap entry for the terminal in use, and by the output baud
rate as known by the kernel. The shell command `stty' will print
your output baud rate; `stty' with suitable arguments will set it if
it is wrong. Setting to a higher speed causes increased padding. If
the results are wrong for the correct speed, there is probably a
problem in the termcap entry. You must speak to a local Unix wizard
to fix this. Perhaps you are just using the wrong terminal type.
For terminals that lack a "no flow control" mode, sometimes just
giving lots of padding will prevent actual generation of flow control
codes. You might as well try it.
If you are really unlucky, your terminal is connected to the computer
through a concentrator which sends XON/XOFF flow control to the
computer, or it insists on sending flow control itself no matter how
much padding you give it. Unless you can figure out how to turn flow
control off on this concentrator (again, refer to your local wizard),
you are screwed! You should have the terminal or concentrator
replaced with a properly designed one. In the mean time, some drastic
measures can make Emacs semi-work.
You can make Emacs ignore C-s and C-q and let the operating system
handle them. To do this on a per-session basis, just type M-x
enable-flow-control RET. You will see a message that C-\ and C-^ are
now translated to C-s and C-q. (Use the same command M-x
enable-flow-control to turn *off* this special mode. It toggles flow
control handling.)
If C-\ and C-^ are inconvenient for you (for example, if one of them
is the escape character of your terminal concentrator), you can choose
other characters by setting the variables flow-control-c-s-replacement
and flow-control-c-q-replacement. But choose carefully, since all
other control characters are already used by emacs.
IMPORTANT: if you type C-s by accident while flow control is enabled,
Emacs output will freeze, and you will have to remember to type C-q in
order to continue.
If you work in an environment where a majority of terminals of a
certain type are flow control hobbled, you can use the function
`enable-flow-control-on' to turn on this flow control avoidance scheme
automatically. Here is an example:
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
and good vt200 terminals), you can still run enable-flow-control
I have no intention of ever redesigning the Emacs command set for the
assumption that terminals use C-s/C-q flow control. XON/XOFF flow
control technique is a bad design, and terminals that need it are bad
merchandise and should not be purchased. Now that X is becoming
widespread, XON/XOFF seems to be on the way out. If you can get some
use out of GNU Emacs on inferior terminals, more power to you, but I
will not make Emacs worse for properly designed systems for the sake
of inferior systems.
* Control-S and Control-Q commands are ignored completely.
For some reason, your system is using brain-damaged C-s/C-q flow
control despite Emacs's attempts to turn it off. Perhaps your
terminal is connected to the computer through a concentrator
that wants to use flow control.
You should first try to tell the concentrator not to use flow control.
If you succeed in this, try making the terminal work without
flow control, as described in the preceding section.
If that line of approach is not successful, map some other characters
into C-s and C-q using keyboard-translate-table. The example above
shows how to do this with C-^ and C-\.
* Control-S and Control-Q commands are ignored completely on a net connection.
Some versions of rlogin (and possibly telnet) do not pass flow
control characters to the remote system to which they connect.
On such systems, emacs on the remote system cannot disable flow
control on the local system.
One way to cure this is to disable flow control on the local host
(the one running rlogin, not the one running rlogind) using the
stty command, before starting the rlogin process. On many systems,
"stty start u stop u" will do this.
Some versions of tcsh will prevent even this from working. One way
around this is to start another shell before starting rlogin, and
issue the stty command to disable flow control from that shell.
If none of these methods work, the best solution is to type
M-x enable-flow-control at the beginning of your emacs session, or
if you expect the problem to continue, add a line such as the
following to your .emacs (on the host running rlogind):
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
See the entry about spontaneous display of I-search (above) for more
* Screen is updated wrong, but only on one kind of terminal.
This could mean that the termcap entry you are using for that
terminal is wrong, or it could mean that Emacs has a bug handing
the combination of features specified for that terminal.
The first step in tracking this down is to record what characters
Emacs is sending to the terminal. Execute the Lisp expression
(open-termscript "./emacs-script") to make Emacs write all
terminal output into the file ~/emacs-script as well; then do
what makes the screen update wrong, and look at the file
and decode the characters using the manual for the terminal.
There are several possibilities:
1) The characters sent are correct, according to the terminal manual.
In this case, there is no obvious bug in Emacs, and most likely you
need more padding, or possibly the terminal manual is wrong.
2) The characters sent are incorrect, due to an obscure aspect
of the terminal behavior not described in an obvious way
by termcap.
This case is hard. It will be necessary to think of a way for
Emacs to distinguish between terminals with this kind of behavior
and other terminals that behave subtly differently but are
classified the same by termcap; or else find an algorithm for
Emacs to use that avoids the difference. Such changes must be
tested on many kinds of terminals.
3) The termcap entry is wrong.
See the file etc/TERMS for information on changes
that are known to be needed in commonly used termcap entries
for certain terminals.
4) The characters sent are incorrect, and clearly cannot be
right for any terminal with the termcap entry you were using.
This is unambiguously an Emacs bug, and can probably be fixed
in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.
* Output from Control-V is slow.
On many bit-map terminals, scrolling operations are fairly slow.
Often the termcap entry for the type of terminal in use fails
to inform Emacs of this. The two lines at the bottom of the screen
before a Control-V command are supposed to appear at the top after
the Control-V command. If Emacs thinks scrolling the lines is fast,
it will scroll them to the top of the screen.
If scrolling is slow but Emacs thinks it is fast, the usual reason is
that the termcap entry for the terminal you are using does not
specify any padding time for the `al' and `dl' strings. Emacs
concludes that these operations take only as much time as it takes to
send the commands at whatever line speed you are using. You must
fix the termcap entry to specify, for the `al' and `dl', as much
time as the operations really take.
Currently Emacs thinks in terms of serial lines which send characters
at a fixed rate, so that any operation which takes time for the
terminal to execute must also be padded. With bit-map terminals
operated across networks, often the network provides some sort of
flow control so that padding is never needed no matter how slow
an operation is. You must still specify a padding time if you want
Emacs to realize that the operation takes a long time. This will
cause padding characters to be sent unnecessarily, but they do
not really cost much. They will be transmitted while the scrolling
is happening and then discarded quickly by the terminal.
Most bit-map terminals provide commands for inserting or deleting
multiple lines at once. Define the `AL' and `DL' strings in the
termcap entry to say how to do these things, and you will have
fast output without wasted padding characters. These strings should
each contain a single %-spec saying how to send the number of lines
to be scrolled. These %-specs are like those in the termcap
`cm' string.
You should also define the `IC' and `DC' strings if your terminal
has a command to insert or delete multiple characters. These
take the number of positions to insert or delete as an argument.
A `cs' string to set the scrolling region will reduce the amount
of motion you see on the screen when part of the screen is scrolled.
* Your Delete key sends a Backspace to the terminal, using an AIXterm.
The solution is to include in your .Xdefaults the lines:
*aixterm.Translations: #override <Key>BackSpace: string(0x7f)
aixterm*ttyModes: erase ^?
This makes your Backspace key send DEL (ASCII 127).
* You type Control-H (Backspace) expecting to delete characters.
Emacs has traditionally used Control-H for help; unfortunately
this interferes with its use as Backspace on TTY's. This has not
been fixed due to an incredible arrogance on RMS's part. One way
to solve this problem is to put this in your .emacs:
(global-set-key "\b" 'delete-backward-char)
(global-set-key "\M-h" 'help-command)
This makes Control-H (Backspace) work sensibly, and moves help to
Meta-H (ESC H).
Note that you can probably also access help using F1.
* Editing files through RFS gives spurious "file has changed" warnings.
It is possible that a change in Emacs 18.37 gets around this problem,
but in case not, here is a description of how to fix the RFS bug that
causes it.
There was a serious pair of bugs in the handling of the fsync() system
call in the RFS server.
The first is that the fsync() call is handled as another name for the
close() system call (!!). It appears that fsync() is not used by very
many programs; Emacs version 18 does an fsync() before closing files
to make sure that the bits are on the disk.
This is fixed by the enclosed patch to the RFS server.
The second, more serious problem, is that fsync() is treated as a
non-blocking system call (i.e., it's implemented as a message that
gets sent to the remote system without waiting for a reply). Fsync is
a useful tool for building atomic file transactions. Implementing it
as a non-blocking RPC call (when the local call blocks until the sync
is done) is a bad idea; unfortunately, changing it will break the RFS
protocol. No fix was supplied for this problem.
(as always, your line numbers may vary)
% rcsdiff -c -r1.2 serversyscall.c
RCS file: RCS/serversyscall.c,v
retrieving revision 1.2
diff -c -r1.2 serversyscall.c
*** /tmp/,RCSt1003677 Wed Jan 28 15:15:02 1987
--- serversyscall.c Wed Jan 28 15:14:48 1987
*** 163,169 ****
* No return sent for close or fsync!
! if (syscall == RSYS_close || syscall == RSYS_fsync)
proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
--- 166,172 ----
* No return sent for close or fsync!
! if (syscall == RSYS_close)
proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
* Vax C compiler bugs affecting Emacs.
You may get one of these problems compiling Emacs:
foo.c line nnn: compiler error: no table entry for op STASG
foo.c: fatal error in /lib/ccom
These are due to bugs in the C compiler; the code is valid C.
Unfortunately, the bugs are unpredictable: the same construct
may compile properly or trigger one of these bugs, depending
on what else is in the source file being compiled. Even changes
in header files that should not affect the file being compiled
can affect whether the bug happens. In addition, sometimes files
that compile correctly on one machine get this bug on another machine.
As a result, it is hard for me to make sure this bug will not affect
you. I have attempted to find and alter these constructs, but more
can always appear. However, I can tell you how to deal with it if it
should happen. The bug comes from having an indexed reference to an
array of Lisp_Objects, as an argument in a function call:
Lisp_Object *args;
... foo (5, args[i], ...)...
putting the argument into a temporary variable first, as in
Lisp_Object *args;
Lisp_Object tem;
tem = args[i];
... foo (r, tem, ...)...
causes the problem to go away.
The `contents' field of a Lisp vector is an array of Lisp_Objects,
so you may see the problem happening with indexed references to that.
* 68000 C compiler problems
Various 68000 compilers have different problems.
These are some that have been observed.
** Using value of assignment expression on union type loses.
This means that x = y = z; or foo (x = z); does not work
if x is of type Lisp_Object.
** "cannot reclaim" error.
This means that an expression is too complicated. You get the correct
line number in the error message. The code must be rewritten with
simpler expressions.
** XCONS, XSTRING, etc macros produce incorrect code.
If temacs fails to run at all, this may be the cause.
Compile this test program and look at the assembler code:
struct foo { char x; unsigned int y : 24; };
lose (arg)
struct foo arg;
test ((int *) arg.y);
If the code is incorrect, your compiler has this problem.
In the XCONS, etc., macros in lisp.h you must replace (a).u.val with
((a).u.val + coercedummy) where coercedummy is declared as int.
This problem will not happen if the m-...h file for your type
of machine defines NO_UNION_TYPE. That is the recommended setting now.
* C compilers lose on returning unions
I hear that some C compilers cannot handle returning a union type.
Most of the functions in GNU Emacs return type Lisp_Object, which is
defined as a union on some rare architectures.
This problem will not happen if the m-...h file for your type
of machine defines NO_UNION_TYPE. That is the recommended setting now.


text:
SEC charges local lawyer with role in stock scam
Luke Zouvas said to help set up pump 'n' dump
Don Bauder 11:30 a.m., April 28
Driscoll Wharf on N. Harbor Dr.
Photo by Gail Powell
Posted July 14, 2011
Don Bauder 11:30 a.m., April 28
Ian Anderson 11 a.m., April 28
Dave Rice 10:30 a.m., April 28
Ian Anderson 10 a.m., April 28
Jay Allen Sanford 9 a.m., April 28
Ken Harrison 8:30 a.m., April 28
Dryw Keltz 9 p.m., April 27
© 2016 San Diego Reader. All rights reserved. No part of this site may be reproduced without our written permission.
Each newsletter subscription means another chance to win!Close


text:
DENVER (AP) -- Peyton Manning threw for three touchdowns and Von Miller had three sacks, as the Denver Broncos defeated the San Diego Chargers 30-23 on Sunday to take a three-game lead in the AFC West.
Manning threw for 270 yards and Miller finished the day with 13 sacks on the season -- most in the NFL.
The Broncos quarterback got off to a slow start, throwing an interception that Eric Weddle returned for a score and an early 7-0 lead. But the Broncos (7-3) took a 10-7 lead early in the second quarter and never trailed again.
Manning won his 148th regular-season game as a starting quarterback, tying John Elway for second on the all-time list. Brett Favre has 186.
The Chargers (4-6) lost for the fifth time in six games.
KKTV firmly believes in freedom of speech for all and we are happy to provide this forum for the community to share opinions and facts. We ask that commenters keep it clean, keep it truthful, stay on topic and be responsible. Comments left here do not necessarily represent the viewpoint of KKTV 11 News.
If you believe that any of the comments on our site are inappropriate or offensive, please tell us by clicking "Report Abuse" and answering the questions that follow. We will review any reported comments promptly.powered by Disqus
Click Here to access the online Public Inspection File
Viewers with disabilities can get assistance accessing this station's FCC Public Inspection File by contacting the station with the information listed below. Questions or concerns relating to the accessibility of the FCC's online public file system should be directed to the FCC at 888-225-5322, 888-835-5322 (TTY), or email@example.com.


text:
Having trouble submitting steelhead, sturgeon report cards on DFG site? Then mail them in
The deadline for returning mandated steelhead and sturgeon report cards was Jan. 31.
If you didn't submit them, you'll receive a note from the Department of Fish and Game.
Last year, I was able to stumble across the reporting site on the DFG's website. I looked long and hard this year but couldn't find anywhere to electronically report the results.
I sent the DFG an e-mail asking where the reporting site could be found. A reply from the DFG directed me to the same site where licenses are purchased and again, there was no section to submit report card results.
I again e-mailed the DFG, including a copy to the director of the department, and explicitly expressed how utterly useless its website was for this reporting purpose and how this online procedure was about the least user-friendly of any site I'd seen.
I've not heard back from the DFG.
So, if you have either the Steelhead Report and Restoration Card or Sturgeon Report Card as part of your 2011 fishing license package, and have yet to report the results, I suggest you get it done now.
If you can't find either reporting system online, as I couldn't, then mail the card to the DFG. Addresses will be printed on the cards.
Special hunt for snow and white-fronted geese
Hunting geese in the Balance of State Zone opened on the fourth Saturday in October and ran for 100 consecutive days, the exception being the Sacramento Valley Special Management Area, where white-fronted goose season closed Dec. 21.
However, there will be an opening of white-fronted geese and snow geese in the Balance of State Zone from Feb. 18-22.
Farmers have been complaining, so the purpose of this late-season special hunt is to reduce crop depredation on private land and push the geese to public land.
Type A and B wildlife areas won't be open to hunting. However, Type C areas and other public lands that allow waterfowl hunting may be open, so you'll need to know the boundaries. The Sacramento Valley Special Management Area also will be closed to the take of white-fronted geese.
There will be a liberal daily bag limit of eight. A hunter can have up to six white or white-fronted geese.
Current fishing
There's probably just enough snow in the higher elevations to make roads impassable to some, but not all, of the lakes.
Lake Camanche: If you can't catch a trout at this lake now, then you aren't holding your head at the right angle. There was a recent plant from the Mt. Lassen Trout Hatchery of 600 pounds at the South Shore ramp and 1,200 pounds at the North Shore ramp. Additionally, a DFG truck showed up and splashed another 2,000 half-pounders at the North Shore. Those planted by the DFG were triploids, meaning the fish are sterile. They grow fast.
Trollers are hammering fish. The North Shore is the closest to get to. Get your boat on the water and begin trolling at the buoy line. The upper region around the Narrows is proving good, as is the lower region around Hat Island and the dam area. Shore casters can fish the coves or off the points with Power Bait, eggs or crawlers to get bit.
Lake Tahoe: The "Big Mack" is a big boat and one you'd more likely see going out under the Golden Gate Bridge than running at Lake Tahoe. Big, in this case, means comfortable, and if it's too cold for you outside, disappear into the cabin to warm up.
Mickey Daniels fires up the diesels of the "Big Mack" when the sky is dark and is letting lines down as much as 350 feet before the first rays of light appear to the east. You're trolling the North Shore region as the sun rises and seemingly cranking the reel forever when you hook up a lake trout — or mackinaw. Limits are common, but so is tagging and releasing the majority. Many five-pounders are kept, but there are much bigger fish to be had, too.
The best thing about going out with Mickey? You're back at the docks by noon.
Bay waters: There are sturgeon to be had in San Pablo Bay and Suisun Bay. The major problem is that both bodies of water remain heavy in salinity levels. That means you have to put up with the critters you don't want to waste bait on because there hasn't been enough fresh water going down the river to reduce the salinity. Finding your bait are crab, kingfish and small starry flounder.
You could even encounter small sharks. In amongst those, however, sturgeon are roaming. Eel, roe and all three shrimp baits are working if you're willing to pick up a whole bunch of bait and wait it out.
Scott's Flat: This lake just above Nevada City doesn't get much boat or camping activity this time of year. That means you can fish for a day and possibly be the only boat on the lake. There has been some success by trollers hauling a flasher trailed by a threaded night crawler. Try down by the dam. The lake is also known for its smallmouth population, and they've been whacking worms and jigs off the points.
Jenkinson Lake: Most anglers call it Sly Park. The winter fishing can be outstanding for mackinaw, rainbows and nice brown trout. One angler working the Narrows nailed a five-pound brown on a Rapala. Those wanting to shore fish can find easy parking and a short hike at the cove at the second dam, where rainbows and mackinaw can be found. Power Bait, eggs and an inflated crawler work well.
Contact George deVilbiss at email@example.com.


text:
22 U.S. Code § 7604 - Authority to consolidate and combine reports
prev | next
With respect to the reports required by this chapter to be submitted by the President, to ensure an efficient use of resources, the President may, in his discretion and notwithstanding any other provision of this chapter, consolidate or combine any of these reports, except for the report required by section 7611 of this title, so long as the required elements of each report are addressed and reported within a 90-day period from the original deadline date for submission of the report specified in this chapter. The President may also enter into contracts with organizations with relevant expertise to develop, originate, or contribute to any of the reports required by this chapter to be submitted by the President, with the exception of the 5-year strategy.
Source(Pub. L. 108–25, § 5,May 27, 2003, 117 Stat. 718; Pub. L. 110–293, § 5,July 30, 2008, 122 Stat. 2922.)
References in Text
This chapter, referred to in text, was in the original "this Act", meaning Pub. L. 108–25, May 27, 2003, 117 Stat. 711, which is classified principally to this chapter. For complete classification of this Act to the Code, see Short Title note set out under section 7601 of this title and Tables.
2008—Pub. L. 110–293inserted ", with the exception of the 5-year strategy" before the period at end.
Delegation of Functions
LII has no control over and does not endorse any external Internet site that contains links to or references LII.


text:
Leo Riding Lion
Product Actions
Germany-based company Steiff has been bringing little ones joy and laughter with their expertly made plush toys since 1880. Children are guaranteed a rocking good time with Steiff's Leo Riding Lion! Crafted of plush tan fur and equipped with wooden handles, the cuddly toy is a mini animal-lovers dream.
- Independently tested; made without harmful or allergenic substances
- Hand-finished by artisans in Giengen, Germany
- Black button eyes and brown felt nose, "Steiff" engraved at wooden rockers, signature brass-plated button and yellow tag at ear
- 33.25" length x 16.25" width x 21.00" height, approximately
- Holds up to 330 lbs., approximately
- Acrylic/cotton; filling: polyester; frame: stainless steel; handles and rockers: wood
- Surface wash
- Imported
Recommended for children aged 4 and up.
Style # 501980732
Need Help? Have Questions? Contact Us.
Please call 1.888.222.7639 to speak with a Customer Service Representative.
We're here to help you:
Monday - Friday, 9 AM - 9 PM (ET)
Saturday - Sunday, 10:30 AM - 7 PM (ET)
If you prefer email, we can be reached anytime at firstname.lastname@example.com.
Free Shipping & Returns on all U.S. Orders. See Details.


text:
BETHESDA, Md., (WUSA) -- Dollar Tree Stores announced a recall of 117,000 glass votive candle holders.
The frosted or clear glass holders can shatter when burning a votive candle, and pose a fire and laceration hazard.
The model number on the 2 1/2 inch votive candle holder is 976127. the date code 1010 are printed on the bottom of the glass holder.
Sold nationwide at Dollar Tree, Dollar Bill$, and Dollar Tree Deal$ stores from December 2010 through April 2011 for about $1.
There have been no reports of injury. Consumers should stop using the candle holders immediately and return them to the store for a full refund.


text:
I'm new to digital scrapbooking and just made my first layout using PSE 6 on my Mac. After saving my files, first my layered .psd, then my flattened jpeg version, I have a couple of questions:
1. I'm wondering if every time I click on the jpeg version of my layout, should it be opening right on my desktop like any other jpeg would, or will it only open in PSE? Right now it's only opening in PSE, and that seems weird to me. I'm thinking that once a layout is finished and converted to jpeg it should become independent of PSE. Correct? If so, what did I do wrong to keep it connected to PSE?
2. I'm also wondering if .psd files are supposed to be HUGE? My finished .psd file of my first layout that was made using a Quick Page and just one photo, is between 60 and 70 megabytes! WOW!! That seems HUGE to me! Is it supposed to be that HUGE? If not, what did I do wrong?
Thanks in advance for any answers... Debbie :confused1:


text:
Cruise.com Cruise Deals
Cruise Lines
Carnival Cruise Line
Celebrity Cruises
Holland America
MSC Cruises
Norwegian Cruise Line
Oceania Cruises
Princess Cruises
Royal Caribbean
Viking River Cruises
See All Cruise Lines
Cruise Deals
Holiday Cruises
Last Minute Cruises
Carnival Cruise Line
Celebrity Cruises
Cunard Line
Holland America Line
MSC Cruises
Norwegian Cruise Line
Oceania Cruises
Princess Cruises
Regent Cruises
Royal Caribbean
Viking River Cruises
See All Cruise Deals
Alaska Cruises
Alaska Cruise Tours
Bahamas Cruises
Bermuda Cruises
Caribbean Cruises
Europe Cruises
Hawaii Cruises
Mediterranean Cruises
Panama Canal Cruises
River Cruises
World Cruises
See All Destinations
Specialty Cruises
Culinary Cruises
Group Cruises
Kids Cruises
Luxury Cruises
Theme Cruises
Wedding Cruises
Wine Cruises
Weekend Cruises
Cruise Ports
Cruise from Baltimore
Cruise from Bayonne
Cruise from Boston
Cruise from Charleston
Cruise from Ft Lauderdale
Cruise from Galveston
Cruise from Miami
Cruise from New Orleans
Cruise from New York
Cruise from Port Canaveral
Cruise from Seattle
Cruise from Tampa
See All Departure Ports
Cruise Info
Passport Requirements
Cruise Tips
Cruise Videos
Cruise Dining
Mobile App
Port Parking
Shore Excursions
Pre & Post Packages
Pre-Cruise Registration
Expectant Mothers
Special Needs
Quote Request
Are you looking for
a Cruise Vacation?
We can't find the page you are requesting but would love to help you find your perfect cruise. We offer cruises on over 70 cruise lines to worldwide destinations so we are sure to have what you are looking for.
Here are just a few suggestions on how to find your dream cruise:
Cruise Destinations
Cruise Lines
Cruise Deals
Cruise Departure Ports
If you are still not sure then visit our
home page
and explore all of the exciting options we offer.
If you prefer, you can speak with one of our expert cruise agents 24/7 at 888-333-3116. We look forward to helping you.
Contact Us
©2016 Cruise.com
Save with our weekly edeals


text:
Scroll to Previous Item
Scroll to Next Item
Border Stripe Yarn Dye Placemat Set
Buy one, get one 50% off of all tabletop and trays with promo code BUY1GET1
No longer available
Crossing borders. Our Border Stripe Placemat Set features stitched edges in contrasting colors. Woven from yarn-dyed cotton, these colorful placemats make everyday dining seem fun.
14"l x 19"w.
100% cotton.
Sets of 2.
Made in India.


text:
8 Inch Steel Toe Boots
There are no products matching the selection.
I just wanted to drop a line and thank you for your professionalism in seeing my order was delivered. This is the third pair of boots I have purchased and not the last. Your products always live up to the description. Just wanted to say thanks to the reps who handled my order. Good job! I do appreciate quality and efficiency!"
Randy R. from Pocahontas, AR


text:
Fearlessness in Difficult Times
An enlightened way to cope with fear requires awakening to courage, love, and compassion.Shambhala Publications.
When I was about six years old I received the essentialbodhichitta
teaching from an old woman sitting in the sun. I was walking by her house one day feeling lonely, unloved, and mad, kicking anything I could find. Laughing, she said to me, "Little girl, don't you go letting life harden your heart."
Right there, I received this pith instruction: We can let the circumstances of our lives harden us so that we become increasingly resentful and afraid, or we can let them soften us and make us kinder and more open to what scares us. We always have this choice. If we were to ask the Buddha, "What is bodhichitta?" he might tell us that this word is easier to understand than to translate. He might encourage us to seek out ways to find its meaning in our own lives. He might tantalize us by adding that it is only bodhichitta that heals, that bodhichitta is capable of transforming the hardest of hearts and the most prejudiced and fearful of minds.
means "mind" and also "heart" or "attitude."Bodhi
means "awake," "enlightened," or "completely open." Sometimes the completely open heart and mind of bodhichitta is called the soft spot, a place as vulnerable and tender as an open wound. It is equated, in part, with our ability to love. Even the most vicious animals love their offspring. As Trungpa Rinpoche put it, "Everybody loves something, even if it's only tortillas."
Bodhichitta is also equated, in part, with compassion--our ability to feel the pain that we share with others. Without realizing it, we continually shield ourselves from this pain because it scares us. We put up protective walls made of opinions, prejudices, and strategies, barriers that are built on a deep fear of being hurt. These walls are further fortified by emotions of all kinds: anger, craving, indifference, jealousy and envy, arrogance and pride. But fortunately for us, the soft spot--our innate ability to love and to care about things--is like a crack in these walls we erect. It's a natural opening in the barriers we create when we're afraid. With practice we can learn to find this opening. We can learn to seize that vulnerable moment--love, gratitude, loneliness, embarrassment, inadequacy--to awaken bodhichitta.
More from Beliefnet


text:
A Musical Note
Making a career choice is challenging. You might ask yourself: "Should I really major in an arts-related field?" "Will I be able to make a living?" "What can ONU offer me that other liberal arts institutions cannot?"
We love to boast about our many successful graduates from the ONU Music Department! These talented individuals and their stories speak for themselves. The "Alumni Profiles" link on this page will connect you with just a few of our thriving graduates who are now forging a path in their musical and artistic arenas.
The ONU Music Department is fully accredited by the National Association of Schools of Music, with abundant opportunities to perform, superb academics, top-notch faculty, excellent ensemble performance experiences, a dynamic musical theater program that provides opportunities to perform on stage and in the pit, and faculty and staff with connections to such venues as the Cleveland Symphony Orchestra, the San Francisco Opera Company, internship experiences with pedagogues such as Malcolm Bilson, and the Climax Jazz Band of Toronto, to name only a few.
We offer a wide variety of programs, Music in Music Performance omit concentrations, the Bachelor of Music in Music Education, or the Bachelor of Arts in Music with concentrations in Theory/Composition, Music History/Literature, or Applied Studies, as well as the music minor.
ONU music faculty hold degrees from such prestigious institutions as The University of Cincinnati's College-Conservatory of Music, The Cleveland Institute of Music, The Oberlin College Conservatory of Music, the Berlin Konservatorium, the Interlochen Arts Academy, The Ohio State University, The University of Arts Berlin, the Jacobs School of Music at Indiana University, The University of Dayton, The "George Dima" Academy of Music in Romania, and Mannes College of Music. Our small class sizes, entrepreneurial approach, accessible and caring faculty, and a vibrant and exciting learning environment ensure that the ONU Music Department provides rigorous challenges to fully equip our students to excel in a competitive musical world. We strive meet students at their current level and help them reach their top potential as musicians, teachers, and scholars.
The ONU Music department also enjoys special study-abroad and student-teaching relationships with the Estonian Academy of Music and the University of Salford in Manchester, England. Our many bands, choirs, and orchestral groups have toured all over the world, including China, Germany, New Zealand, Estonia, Rome, Spain and Mexico, just to mention a few.
Audition in person: January 17, January 31, February 14, February 21, March 14, 2015. You can also audition by appointment, or upload your audition at any time on Acceptd.com on our website from wherever you are, all over the world. Substantial talent and academic awards are available through a successful audition. An overnight stay with one of our music majors is always recommended—get a real taste of our college and campus life! We can arrange for you to have lessons with our superb faculty, attend classes, and observe our rehearsals and performances.
For our musician friends who are not music majors but who wish to continue their musical experiences, there are non-major talent awards available by audition. Contact Dr. Rebecca Casey for details, and upload your audition on Acceptd.com. Deadline is February 28, 2015.
Schedule your audition HERE today! We look forward to meeting you!
Dr. Rebecca L. Casey, N.C.T.M.
Chair, ONU Music


text:
order by phone... 1-800-828-4548
order by item number...add items to my cart
Browse more:
These clear glue sticks can be used with either low temperature or high temperature glue guns.
Please select one of your Lists or create a new List.
Your cart is currently empty.
® Surebonder is a registered trademark of FPC Corporation.
Dick Blick Art Materials®, Blick®, Blick Studio®, and Artists Pick Blick® are registered trademarks of Dick Blick Holdings Inc.
© Copyright 1999-2016 Dick Blick Holdings Inc. All rights reserved.