* fancy splash screen @ 2006-09-14 8:45 martin rudalics 2006-09-14 17:47 ` Chong Yidong 2006-09-15 3:14 ` Richard Stallman 0 siblings, 2 replies; 17+ messages in thread From: martin rudalics @ 2006-09-14 8:45 UTC (permalink / raw) Thanks for making the fancy splash screen persistent for copying. I noticed a couple of minor issues: (1) The line "You can do basic editing with the menu bar and scroll bar using the mouse." occurs twice. That seems unprofessional. (2) The items below do not line up well with proportional font. I'd use Important Help menu items: Emacs Tutorial Learn how to use Emacs efficiently (Einführung in Emacs) Emacs FAQ Frequently asked questions and answers (Non)Warranty GNU Emacs comes with ABSOLUTELY NO WARRANTY Get New Versions How to obtain the latest version of Emacs Copying Conditions Conditions for redistributing and changing Emacs Read the Emacs Manual View the Emacs manual using Info More Manuals / Ordering Manuals Buying printed manuals from the FSF instead (replacing "Getting ..." by "Get ..." in the Help menu as well). (3) I'd interchange the following two lines Exit Emacs (Or type Control-x followed by Control-c) Recover Crashed Session Recover files you were editing before a crash while trying to combine the "Recover ..." line with the closing "If an Emacs session crashed recently, type M-x recover-session RET to recover the files you were editing." provided the auto-save-list directory exists, and write Meta-x instead of M-x. (4) On my system the Copyright Notice is hardly visible. The :height 0.5 option scales very badly and should be removed. (5) The text of `fancy-splash-help-echo' should appear permanently on the splash screen and not annoyingly pop up via tooltips (which on some systems might not even be present). This holds for the help-echo on the image as well. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-14 8:45 fancy splash screen martin rudalics @ 2006-09-14 17:47 ` Chong Yidong 2006-09-15 3:14 ` Richard Stallman 1 sibling, 0 replies; 17+ messages in thread From: Chong Yidong @ 2006-09-14 17:47 UTC (permalink / raw) Cc: emacs-devel martin rudalics <rudalics@gmx.at> writes: > (1) The line > > "You can do basic editing with the menu bar and scroll bar using the > mouse." > > occurs twice. That seems unprofessional. I've fixed this. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-14 8:45 fancy splash screen martin rudalics 2006-09-14 17:47 ` Chong Yidong @ 2006-09-15 3:14 ` Richard Stallman 2006-09-15 12:19 ` martin rudalics 1 sibling, 1 reply; 17+ messages in thread From: Richard Stallman @ 2006-09-15 3:14 UTC (permalink / raw) Cc: emacs-devel I improved the alignment of the items. (5) The text of `fancy-splash-help-echo' should appear permanently on the splash screen and not annoyingly pop up via tooltips (which on some systems might not even be present). This holds for the help-echo on the image as well. Do you mean the statement about C-h C-p? I made it display that only in the echo area. (4) On my system the Copyright Notice is hardly visible. The :height 0.5 option scales very badly and should be removed. It is quite visible on my system; what makes it so hard to see on your system? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 3:14 ` Richard Stallman @ 2006-09-15 12:19 ` martin rudalics 2006-09-15 13:02 ` Romain Francoise ` (2 more replies) 0 siblings, 3 replies; 17+ messages in thread From: martin rudalics @ 2006-09-15 12:19 UTC (permalink / raw) Cc: emacs-devel > (5) The text of `fancy-splash-help-echo' should appear permanently on > the splash screen and not annoyingly pop up via tooltips (which on some > systems might not even be present). This holds for the help-echo on the > image as well. > > Do you mean the statement about C-h C-p? Yes. > I made it display that only in the echo area. Wouldn't that distract from other messages displayed during startup? I'd display that at the bottom of the splash screen together with the URL that pops up when hovering over the image. > (4) On my system the Copyright Notice is hardly visible. The :height > 0.5 option scales very badly and should be removed. > > It is quite visible on my system; what makes it so hard to see on your > system? Apparently, I don't have the appropriate Arial font installed (I don't care much about proportional fonts). With the fonts supplied on my system it scales to about one fourth of the remaining text. If the copyright notice is of any importance here, it should have the same size as the remainder of the text I think. BTW, I'd prefer calling the "GNU Emacs" buffer either "*splash-screen*" or " *splash-screen*". ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 12:19 ` martin rudalics @ 2006-09-15 13:02 ` Romain Francoise 2006-09-15 13:06 ` David Kastrup 2006-09-15 22:57 ` Richard Stallman 2006-09-15 22:57 ` Richard Stallman 2 siblings, 1 reply; 17+ messages in thread From: Romain Francoise @ 2006-09-15 13:02 UTC (permalink / raw) Cc: rms, emacs-devel martin rudalics <rudalics@gmx.at> writes: > BTW, I'd prefer calling the "GNU Emacs" buffer either > "*splash-screen*" or " *splash-screen*". Or "*About Emacs*"... -- Romain Francoise <romain@orebokech.com> | The sea! the sea! the open it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the | ever free! --Bryan W. Procter ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 13:02 ` Romain Francoise @ 2006-09-15 13:06 ` David Kastrup 2006-09-15 14:12 ` martin rudalics 2006-09-15 14:12 ` Drew Adams 0 siblings, 2 replies; 17+ messages in thread From: David Kastrup @ 2006-09-15 13:06 UTC (permalink / raw) Cc: martin rudalics, rms, emacs-devel Romain Francoise <romain@orebokech.com> writes: > martin rudalics <rudalics@gmx.at> writes: > >> BTW, I'd prefer calling the "GNU Emacs" buffer either >> "*splash-screen*" or " *splash-screen*". > > Or "*About Emacs*"... Emacs is somewhat redundant. *About* would probably be fine. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 13:06 ` David Kastrup @ 2006-09-15 14:12 ` martin rudalics 2006-09-15 15:17 ` David Kastrup 2006-09-15 14:12 ` Drew Adams 1 sibling, 1 reply; 17+ messages in thread From: martin rudalics @ 2006-09-15 14:12 UTC (permalink / raw) Cc: Romain Francoise, rms, emacs-devel > *About* > > would probably be fine. > *Splash* ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 14:12 ` martin rudalics @ 2006-09-15 15:17 ` David Kastrup 2006-09-16 19:05 ` Richard Stallman 0 siblings, 1 reply; 17+ messages in thread From: David Kastrup @ 2006-09-15 15:17 UTC (permalink / raw) Cc: Romain Francoise, rms, emacs-devel martin rudalics <rudalics@gmx.at> writes: >> *About* >> >> would probably be fine. >> > > *Splash* We use "About Emacs" in the Help menu, exactly because "About" is common usage for that functionality. I don't really think that it makes sense to call this buffer something which nobody will identify. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 15:17 ` David Kastrup @ 2006-09-16 19:05 ` Richard Stallman 0 siblings, 0 replies; 17+ messages in thread From: Richard Stallman @ 2006-09-16 19:05 UTC (permalink / raw) Cc: rudalics, romain, emacs-devel The buffer name was chosen to be appropriate in the mode line at startup. But now I see the issue is what to call the buffer when the About menu item is used. I will change it to *About GNU Emacs*. ^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: fancy splash screen 2006-09-15 13:06 ` David Kastrup 2006-09-15 14:12 ` martin rudalics @ 2006-09-15 14:12 ` Drew Adams 2006-09-15 15:21 ` David Kastrup 1 sibling, 1 reply; 17+ messages in thread From: Drew Adams @ 2006-09-15 14:12 UTC (permalink / raw) >> BTW, I'd prefer calling the "GNU Emacs" buffer either >> "*splash-screen*" or " *splash-screen*". > Or "*About Emacs*"... Emacs is somewhat redundant. *About* would probably be fine. "About Emacs" describes what it is. "About GNU Emacs" would be better, providing a helpful reminder about GNU (but some will argue that GNU is never needed in "GNU Emacs"). "Emacs" in "About Emacs" is not redundant in any way. If you have multiple buffers, there is nothing that implies that one named only "About" has help about Emacs. Is it good or bad to use "*...*"? I don't know. I tend to think it's not needed here. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 14:12 ` Drew Adams @ 2006-09-15 15:21 ` David Kastrup 2006-09-15 16:00 ` Drew Adams 0 siblings, 1 reply; 17+ messages in thread From: David Kastrup @ 2006-09-15 15:21 UTC (permalink / raw) Cc: emacs-devel "Drew Adams" <drew.adams@oracle.com> writes: > >> BTW, I'd prefer calling the "GNU Emacs" buffer either > >> "*splash-screen*" or " *splash-screen*". > > Or "*About Emacs*"... > > Emacs is somewhat redundant. > *About* would probably be fine. > > "About Emacs" describes what it is. "About GNU Emacs" would be > better, providing a helpful reminder about GNU (but some will argue > that GNU is never needed in "GNU Emacs"). It is not needed in general. It can be nice to stress its role in the GNU project when talking about that, but I think that in purely technical contexts, just "Emacs" is the more straightforward use. > "Emacs" in "About Emacs" is not redundant in any way. If you have > multiple buffers, there is nothing that implies that one named only > "About" has help about Emacs. Most applications I know have exactly one "About" menu, and Emacs does not seem to be different in that respect. > Is it good or bad to use "*...*"? I don't know. I tend to think it's > not needed here. Standard naming convention for buffers without associated files. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: fancy splash screen 2006-09-15 15:21 ` David Kastrup @ 2006-09-15 16:00 ` Drew Adams 2006-09-15 16:22 ` David Kastrup 0 siblings, 1 reply; 17+ messages in thread From: Drew Adams @ 2006-09-15 16:00 UTC (permalink / raw) > "Emacs" in "About Emacs" is not redundant in any way. If you have > multiple buffers, there is nothing that implies that one named only > "About" has help about Emacs. Most applications I know have exactly one "About" menu, and Emacs does not seem to be different in that respect. It's not about the menu; it's about the buffer name. There are lots of buffers whose content is "about" something, and some Emacs libraries might use that term in buffer names, for various purposes. You might have buffers "*About Foo Bar*" and "*About Toto*". The buffer about Emacs should be called "*About Emacs*" (possibly with "GNU"). A buffer name of just "*About*" does not clearly indicate what it is. > Is it good or bad to use "*...*"? I don't know. I tend to think it's > not needed here. Standard naming convention for buffers without associated files. Right. Thx. So "GNU Emacs" was also a poor choice for the buffer name for that reason. BTW, I think I've read about that convention explicitly somewhere, but I can't seem to find it in the Elisp manual. Shouldn't that be mentioned in node Tips or node Coding Conventions? Similarly, I don't see it mentioned in the Emacs manual. Shouldn't it be mentioned along with the use of space as first character for internal buffers (e.g. in node Select Buffer)? Node Buffers is perhaps a good place to mention use of both `*' and initial space in buffer names. That node gives examples of `*' buffers, without ever pointing out that they are buffers that are not normally visiting files. Another possibility is node List Buffers, which points out that *Help* is not visiting a file (but does not make the connection with `*' in the name). ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 16:00 ` Drew Adams @ 2006-09-15 16:22 ` David Kastrup 2006-09-15 16:43 ` Drew Adams 0 siblings, 1 reply; 17+ messages in thread From: David Kastrup @ 2006-09-15 16:22 UTC (permalink / raw) Cc: emacs-devel "Drew Adams" <drew.adams@oracle.com> writes: > > "Emacs" in "About Emacs" is not redundant in any way. If you have > > multiple buffers, there is nothing that implies that one named only > > "About" has help about Emacs. > > Most applications I know have exactly one "About" menu, and Emacs does > not seem to be different in that respect. > > It's not about the menu; it's about the buffer name. There are lots > of buffers whose content is "about" something, and some Emacs > libraries might use that term in buffer names, for various > purposes. You might have buffers "*About Foo Bar*" and "*About > Toto*". But we don't have any such buffers. This seems academical. > The buffer about Emacs should be called "*About Emacs*" (possibly > with "GNU"). A buffer name of just "*About*" does not clearly > indicate what it is. As I said: having a single "About" item is common for applications. Since the menu entry is called "About Emacs", calling the buffer "*About Emacs*" seems a suitable choice. I don't find your arguments for that name persuasive at all, but since I am fine with that choice, it seems useless to haggle over just _why_. > Similarly, I don't see it mentioned in the Emacs manual. Shouldn't > it be mentioned along with the use of space as first character for > internal buffers (e.g. in node Select Buffer)? Node Buffers is > perhaps a good place to mention use of both `*' and initial space in > buffer names. That node gives examples of `*' buffers, without ever > pointing out that they are buffers that are not normally visiting > files. It is basically only a convention, but it might be worth mentioning there or somewhere else. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: fancy splash screen 2006-09-15 16:22 ` David Kastrup @ 2006-09-15 16:43 ` Drew Adams 0 siblings, 0 replies; 17+ messages in thread From: Drew Adams @ 2006-09-15 16:43 UTC (permalink / raw) > > "Emacs" in "About Emacs" is not redundant in any way. > > If you have multiple buffers, there is nothing that > > implies that one named only "About" has help about Emacs. > > Most applications I know have exactly one "About" menu, > and Emacs does not seem to be different in that respect. > > It's not about the menu; it's about the buffer name. There are lots > of buffers whose content is "about" something, and some Emacs > libraries might use that term in buffer names, for various > purposes. You might have buffers "*About Foo Bar*" and "*About > Toto*". But we don't have any such buffers. This seems academical. "We" who? Users may use such buffers. Other libraries may use such buffers. > The buffer about Emacs should be called "*About Emacs*" (possibly > with "GNU"). A buffer name of just "*About*" does not clearly > indicate what it is. As I said: having a single "About" item is common for applications. As I said, it's not about the menu-item name, or the number of menu items per application, or the number of applications; it's about the buffer name. Since the menu entry is called "About Emacs", calling the buffer "*About Emacs*" seems a suitable choice. So we agree. I don't find your arguments for that name persuasive at all, but since I am fine with that choice, it seems useless to haggle over just _why_. Good. > Similarly, I don't see it mentioned in the Emacs manual. Shouldn't > it be mentioned along with the use of space as first character for > internal buffers (e.g. in node Select Buffer)? Node Buffers is > perhaps a good place to mention use of both `*' and initial space in > buffer names. That node gives examples of `*' buffers, without ever > pointing out that they are buffers that are not normally visiting > files. It is basically only a convention, but it might be worth mentioning there or somewhere else. It should be mentioned in the conventions section of the Elisp manual, if it is a convention that we would like programmers to use. If it is useful for users to understand this naming convention (and it must be; otherwise, why use it for user-visible names?), then it should also be pointed out in the Emacs manual. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 12:19 ` martin rudalics 2006-09-15 13:02 ` Romain Francoise @ 2006-09-15 22:57 ` Richard Stallman 2006-09-15 22:57 ` Richard Stallman 2 siblings, 0 replies; 17+ messages in thread From: Richard Stallman @ 2006-09-15 22:57 UTC (permalink / raw) Cc: emacs-devel > I made it display that only in the echo area. Wouldn't that distract from other messages displayed during startup? That doesn't make sense to me; I don't see why text in the echo area would distract attention from text in the buffer. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 12:19 ` martin rudalics 2006-09-15 13:02 ` Romain Francoise 2006-09-15 22:57 ` Richard Stallman @ 2006-09-15 22:57 ` Richard Stallman 2006-09-16 12:55 ` martin rudalics 2 siblings, 1 reply; 17+ messages in thread From: Richard Stallman @ 2006-09-15 22:57 UTC (permalink / raw) Cc: emacs-devel BTW, I'd prefer calling the "GNU Emacs" buffer either "*splash-screen*" or " *splash-screen*". The string appears in the mode line, and "GNU Emacs" seems appropriate for the string to display there. Your proposals would be good in a different context. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: fancy splash screen 2006-09-15 22:57 ` Richard Stallman @ 2006-09-16 12:55 ` martin rudalics 0 siblings, 0 replies; 17+ messages in thread From: martin rudalics @ 2006-09-16 12:55 UTC (permalink / raw) Cc: emacs-devel > The string appears in the mode line, and "GNU Emacs" seems appropriate > for the string to display there. Your proposals would be good in a > different context. But "GNU Emacs" is distracting in the context of buffer listings. It does not visit a file. Would "*GNU Emacs*" be OK? ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2006-09-16 19:05 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-09-14 8:45 fancy splash screen martin rudalics 2006-09-14 17:47 ` Chong Yidong 2006-09-15 3:14 ` Richard Stallman 2006-09-15 12:19 ` martin rudalics 2006-09-15 13:02 ` Romain Francoise 2006-09-15 13:06 ` David Kastrup 2006-09-15 14:12 ` martin rudalics 2006-09-15 15:17 ` David Kastrup 2006-09-16 19:05 ` Richard Stallman 2006-09-15 14:12 ` Drew Adams 2006-09-15 15:21 ` David Kastrup 2006-09-15 16:00 ` Drew Adams 2006-09-15 16:22 ` David Kastrup 2006-09-15 16:43 ` Drew Adams 2006-09-15 22:57 ` Richard Stallman 2006-09-15 22:57 ` Richard Stallman 2006-09-16 12:55 ` martin rudalics
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).