148 lines
46 KiB
HTML
148 lines
46 KiB
HTML
<!DOCTYPE html>
|
||
<html><head><title>EmacsWiki: Emacs Wiki Suggestions</title><link rel="alternate" type="application/wiki" title="Edit this page" href="https://www.emacswiki.org/emacs?action=edit;id=EmacsWikiSuggestions" /><link type="text/css" rel="stylesheet" href="https://www.emacswiki.org/light.css" /><meta name="robots" content="INDEX,FOLLOW" /><link rel="alternate" type="application/rss+xml" title="EmacsWiki" href="https://www.emacswiki.org/emacs?action=rss" /><link rel="alternate" type="application/rss+xml" title="EmacsWiki: EmacsWikiSuggestions" href="https://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions" />
|
||
<link rel="alternate" type="application/rss+xml"
|
||
title="Emacs Wiki with page content"
|
||
href="https://www.emacswiki.org/full.rss" />
|
||
<link rel="alternate" type="application/rss+xml"
|
||
title="Emacs Wiki with page content and diff"
|
||
href="https://www.emacswiki.org/full-diff.rss" />
|
||
<link rel="alternate" type="application/rss+xml"
|
||
title="Emacs Wiki including minor differences"
|
||
href="https://www.emacswiki.org/minor-edits.rss" />
|
||
<link rel="alternate" type="application/rss+xml"
|
||
title="Changes for EmacsWikiSuggestions only"
|
||
href="https://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions" /><meta content="width=device-width" name="viewport" />
|
||
<script type="text/javascript" src="/outliner-toc.js"></script>
|
||
<script type="text/javascript">
|
||
|
||
function addOnloadEvent(fnc) {
|
||
if ( typeof window.addEventListener != "undefined" )
|
||
window.addEventListener( "load", fnc, false );
|
||
else if ( typeof window.attachEvent != "undefined" ) {
|
||
window.attachEvent( "onload", fnc );
|
||
}
|
||
else {
|
||
if ( window.onload != null ) {
|
||
var oldOnload = window.onload;
|
||
window.onload = function ( e ) {
|
||
oldOnload( e );
|
||
window[fnc]();
|
||
};
|
||
}
|
||
else
|
||
window.onload = fnc;
|
||
}
|
||
}
|
||
|
||
// https://stackoverflow.com/questions/280634/endswith-in-javascript
|
||
if (typeof String.prototype.endsWith !== 'function') {
|
||
String.prototype.endsWith = function(suffix) {
|
||
return this.indexOf(suffix, this.length - suffix.length) !== -1;
|
||
};
|
||
}
|
||
|
||
var initToc=function() {
|
||
|
||
var outline = HTML5Outline(document.body);
|
||
if (outline.sections.length == 1) {
|
||
outline.sections = outline.sections[0].sections;
|
||
}
|
||
|
||
if (outline.sections.length > 1
|
||
|| outline.sections.length == 1
|
||
&& outline.sections[0].sections.length > 0) {
|
||
|
||
var toc = document.getElementById('toc');
|
||
|
||
if (!toc) {
|
||
var divs = document.getElementsByTagName('div');
|
||
for (var i = 0; i < divs.length; i++) {
|
||
if (divs[i].getAttribute('class') == 'toc') {
|
||
toc = divs[i];
|
||
break;
|
||
}
|
||
}
|
||
}
|
||
|
||
if (!toc) {
|
||
var h2 = document.getElementsByTagName('h2')[0];
|
||
if (h2) {
|
||
toc = document.createElement('div');
|
||
toc.setAttribute('class', 'toc');
|
||
h2.parentNode.insertBefore(toc, h2);
|
||
}
|
||
}
|
||
|
||
if (toc) {
|
||
var html = outline.asHTML(true);
|
||
toc.innerHTML = html;
|
||
|
||
items = toc.getElementsByTagName('a');
|
||
for (var i = 0; i < items.length; i++) {
|
||
while (items[i].textContent.endsWith('✎')) {
|
||
var text = items[i].childNodes[0].nodeValue;
|
||
items[i].childNodes[0].nodeValue = text.substring(0, text.length - 1);
|
||
}
|
||
}
|
||
}
|
||
}
|
||
}
|
||
|
||
addOnloadEvent(initToc);
|
||
</script>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body class="default" lang="en"><header><a class="logo" href="https://www.emacswiki.org/emacs/SiteMap"><img alt="[Home]" class="logo" src="https://www.emacswiki.org/images/logo218x38.png" /></a><nav><span class="gotobar bar"><a class="local" href="https://www.emacswiki.org/emacs/SiteMap">SiteMap</a> <a class="local" href="https://www.emacswiki.org/emacs/Search">Search</a> <a class="local" href="https://www.emacswiki.org/emacs/ElispArea">ElispArea</a> <a class="local" href="https://www.emacswiki.org/emacs/HowTo">HowTo</a> <a class="local" href="https://www.emacswiki.org/emacs/Glossary">Glossary</a> <a class="local" href="https://www.emacswiki.org/emacs/RecentChanges">RecentChanges</a> <a class="local" href="https://www.emacswiki.org/emacs/News">News</a> <a class="local" href="https://www.emacswiki.org/emacs/Problems">Problems</a> <a class="local" href="https://www.emacswiki.org/emacs/Suggestions">Suggestions</a> <a href="https://www.emacswiki.org/emacs?action=random" rel="nofollow">Random</a></span><form method="get" action="https://www.emacswiki.org/emacs" enctype="multipart/form-data" accept-charset="utf-8" class="search"><p><label for="search">Search:</label> <input type="text" name="search" size="15" accesskey="f" id="search" /> <label for="searchlang">Language:</label> <input type="text" name="lang" size="5" id="searchlang" /> <input type="submit" name="dosearch" value="Go!" /></p></form></nav><h1><a href="https://www.emacswiki.org/emacs?search=%22EmacsWikiSuggestions%22" rel="nofollow" title="Click to search for references to this page"><span style="padding-right: 0.5ex;">Emacs</span><span style="padding-right: 0.5ex;">Wiki</span><span style="padding-right: 0.5ex;">Suggestions</span></a></h1></header><div class="wrapper"><div class="content browse" lang="en"><p>This page is for recording (or discussion) of <a class="definition" href="https://www.emacswiki.org/emacs?search=%22Suggestions%22" name="Suggestions" rel="nofollow" title="Click to search for references to this permanent anchor">Suggestions</a> about the <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">EmacsWiki</a> web site.</p><p>If you want to suggest changes to a particular page, or if you want to suggest a new page, please just do it. You don’t need to create an account to do it.</p><p>If you want to record or discuss problems with the Web site (not with Emacs), please do so at <a class="local" href="https://www.emacswiki.org/emacs/EmacsWikiProblems">EmacsWikiProblems</a>.</p><p>Make sure your suggestion doesn’t exist already or that your question has already been answered by checking the <a class="local" href="https://www.emacswiki.org/emacs/HowTo">HowTo</a> and <a class="local" href="https://www.emacswiki.org/emacs/WikiQuestions">WikiQuestions</a> pages, respectively.</p><p>Discussion about the front page of the Wiki is at <a class="local" href="https://www.emacswiki.org/emacs/SiteMap_Discussion">SiteMap Discussion</a>.</p><p>Discussion about the table of contents at the top of each page is at <a class="local" href="https://www.emacswiki.org/emacs/TableOfContentsDiscussion">TableOfContentsDiscussion</a>.</p><p>Discussion about the “Goto Bar”, the links at the top and bottom of each page, is at <a class="local" href="https://www.emacswiki.org/emacs/GotoBarDiscussion">GotoBarDiscussion</a>.</p><p>Discussion about the <a class="local" href="https://www.emacswiki.org/emacs/TextFormattingRules">TextFormattingRules</a> used in contributing to pages is at <a class="local" href="https://www.emacswiki.org/emacs/TextFormattingDiscussion">TextFormattingDiscussion</a>.</p><p><strong>Add your suggestions below this line.</strong> </p><h2>Does anyone object to me removing XEmacs references?</h2><p>Hi. The wiki still prominently refers to XEmacs, which is dead. Users aware of the current Emacs landscape get the impression that the wiki is stale. And clueless users might even install XEmacs and be disappointed with the whole Emacs concept. So, does anyone object to me removing as many XEmacs references as my time and energy permit?</p><div class="color one level0"><p> Thanks for asking before just doing it. Yes, I object.</p><p>I don’t object to updating such text, to make clear that it describes an Emacs implementation that is no longer under development (and that is used by very few Emacs users).</p><p>I don’t object to removal of some how-to information that could no longer be used by anyone.</p><p>The point is that this site is about <strong>Emacs</strong>, not only <a class="local" href="https://www.emacswiki.org/emacs/GnuEmacs">GnuEmacs</a>, and the site contains information about the history of Emacs and its different implementations, as well as references to other such info. There’s even a whole category about this (<a class="local" href="https://www.emacswiki.org/emacs/CategoryHistory">CategoryHistory</a>), and pages about the GNU/XEmacs split (<a class="local" href="https://www.emacswiki.org/emacs/EmacsSchism">EmacsSchism</a>, <a class="local" href="https://www.emacswiki.org/emacs/EmacsAndXEmacs">EmacsAndXEmacs</a>, <a class="local" href="https://www.emacswiki.org/emacs/EmacsSchismDiscussion">EmacsSchismDiscussion</a>).</p><p>In posing the question, you’d maybe be better off saying also which content you’d like to remove, and if not obvious, say how you think it might mislead readers rather than helping them.</p><p>Just one opinion.</p></div><div class="color two level0"><p> Yeah, it’s a bit like documentation for code that is now obsolete, but if somebody were to search for information about Emacs 19 and MULE, for example, where would they find it? Sure, it’s obsolete, but it’s still interesting. It’s no longer “How To” information, but I’d still like to keep it. Like Drew, I’d love pages to be rewritten such as to clearly state what is and what isn’t obsolete, and I would love long pages containing both obsolete and current information to be split into two pages, with the obsolete stuff being relegated to the Talk page, or to a separate page altogether. As a final consideration, I’d say that rewriting pages such that they are more useful for current users than for future historians is more important. So I wouldn’t spend too much time on making the obsolete material nice to read. All I’m saying is that if at all possible, let’s keep it somewhere. – <a class="local" href="https://www.emacswiki.org/emacs/Alex_Schroeder">Alex Schroeder</a></p></div><div class="color one level0"><p> FWIW - I agree with all that Alex has said. – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p></div><h2>Is it worth it to create a Category Logging?</h2><p>I am starting to write a few simple log functions (for debugging variables, etc in Emacs), and I have some questions about it, and I saw <a class="local" href="https://www.emacswiki.org/emacs/Log4E_Logging_For_Elisp">Log4E Logging For Elisp</a> - does it make sense to have <a class="local" href="https://www.emacswiki.org/emacs/CategoryLogging">CategoryLogging</a> for these things? – <a class="local" href="https://www.emacswiki.org/emacs/halloleo">halloleo</a></p><div class="color one level0"><p> No, I don’t think so. I added <a class="local" href="https://www.emacswiki.org/emacs/Log4E_Logging_For_Elisp">Log4E Logging For Elisp</a> to <a class="local" href="https://www.emacswiki.org/emacs/CategoryDebug">CategoryDebug</a>. – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p></div><h2>Revamp the GnuPlot pages</h2><p>The page ‘<a class="local" href="https://www.emacswiki.org/emacs/GnuPlot">GnuPlot</a>’ [<a class="url https number" href="https://www.emacswiki.org/emacs/GnuPlot"><span><span class="bracket">[</span>1<span class="bracket">]</span></span></a>] gives a good two sentence description of gnuplot. But then everything after is out of date. It used to tell how to get the mode written by (dead link)<a class="local" href="https://www.emacswiki.org/emacs/BruceRavel">BruceRavel</a> and a screenshot of the mode.</p><p>If everything after the first two sentences were replaced with a link to ‘<a class="local" href="https://www.emacswiki.org/emacs/GnuplotModes">GnuplotModes</a>’ [<a class="url https number" href="https://www.emacswiki.org/emacs/GnuplotModes"><span><span class="bracket">[</span>2<span class="bracket">]</span></span></a>] that would restore it well. It has updated links to the Mr. Ravel’s mode. It also has links to a second mode.</p><p>It could also use a link to a third mode, ‘<a class="local" href="https://www.emacswiki.org/emacs/GnuplotMode">GnuplotMode</a>’ [<a class="url https number" href="https://www.emacswiki.org/emacs/GnuplotMode"><span><span class="bracket">[</span>3<span class="bracket">]</span></span></a>].</p><h2>Default font-size should not be 1.2em</h2><p>The new CSS is a very nice improvement, but the default font-size is set to 1.2em. This causes all fonts on the page to be 20% larger than the user’s default font size. For me, this is jarring and annoying, causing me to have to scan more and scroll more to read the same amount of text. I have the default font size set to be comfortable for me, and web sites should generally respect users’ default font size. So, please consider setting the <code>body</code> element’s <code>font-size</code> to <code>100%</code> in the stylesheet.</p><div class="color one level0"><p> There’s a <a class="url https outside" href="https://github.com/bburns/emacswiki-light-theme">github repo</a> for the new css, so I think that it would be better to place your suggestion there. I created a <a class="url https outside" href="https://github.com/bburns/emacswiki-light-theme/issues/13">new issue just for that</a>.</p></div><div class="color two level0"><p> Good point - I’ll set the size to 100%, as it’s easy enough for users to override, and there was only one other (positive) comment on the font size - I just tend to like larger fonts as my eyes get older. 😊</p></div><h2>Alt key problem when using Compiz in Ubuntu</h2><p>In Ubuntu (at least when using Compiz), the left Alt key brings up a HUD by default. This causes problems when you use left Alt as the meta key. Hence, this problem should go under the GNU/Linux section in the <a class="local" href="https://www.emacswiki.org/emacs/MetaKeyProblems">Meta Key Problems</a> article. One solution to this problem is to disable a keyboard shortcut to display the HUD, described <a class="url http outside" href="http://askubuntu.com/a/122232">here</a>.</p><h2>Camel Case Auto-split Syntax</h2><div class="color one level0"><p> I think a syntax like ^EmacsWiki to automatically generate a link with spacing like <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">Emacs Wiki</a> would improve the overall look of the site quite a bit. On the main navigation bar for example, “Site Map,” “Elisp Area,” and “Recent Changes” would look much nicer.</p><p>--<a class="local" href="https://www.emacswiki.org/emacs/MikeAbrahams">MikeAbrahams</a></p></div><div class="color two level0"><div class="portrait"><p><a class="newauthor" href="https://www.emacswiki.org/emacs/JimThompson" title="2016-04-15 09:39 UTC"><img alt="new: 2016-04-15 09:39 UTC" class="portrait" src="https://www.emacswiki.org/pics/static/JimThompsonPortrait" /></a> <br /> <a class="local" href="https://www.emacswiki.org/emacs/JimThompson">JimThompson</a></p></div><p> I second this suggestion. --<a class="local" href="https://www.emacswiki.org/emacs/JimThompson">JimThompson</a></p></div><div class="color one level0"><p> I wonder whether I understood this correctly. You can always create link to pages containing spaces using double square brackets <code>[[Like This]]</code>. And we should totally encourage people to do that, and to redirect from pages <code>LikeThis</code> to pages <code>[[Like This]]</code>. Are you arguing that typing <code>^LikeThis</code> is much easier than <code>[[Like This]]</code> or were you unaware of the double square bracket syntax, or did I miss something? – <a class="local" href="https://www.emacswiki.org/emacs/Alex_Schroeder">Alex Schroeder</a></p></div><h2>Provide alternate stylesheets</h2><p>I would like to choose the stylesheet for <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">EmacsWiki</a> easily. If Emacswiki could provide alternate stylesheets—see <a class="url http outside" href="http://orgmode.org/worg/">Worg</a>—then I will be able to choose the theme using View->Page Style->etc menu in Firefox. – <a class="local" href="https://www.emacswiki.org/emacs/115.241.16.57">115.241.16.57</a></p><div class="color one level0"><p> Does <a class="local" href="https://www.emacswiki.org/emacs/CSS">CSS</a> correspond to your request? I don’t use alternative stylesheets myself, but last time I tried this (years ago) it seemed to do what you are suggesting.</p><p>(I’ve updated <a class="local" href="https://www.emacswiki.org/emacs/HowTo">HowTo</a> to mention page <a class="local" href="https://www.emacswiki.org/emacs/CSS">CSS</a>.) – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p></div><div class="color two level0"><p>This is how the directives on <a class="url http outside" href="http://Orgmode.org/worg">Worg</a> looks like:</p><pre> <link rel=<span class="string">"stylesheet"</span> title=<span class="string">"Standard"</span> href=<span class="string">"/worg/style/worg.css"</span> type=<span class="string">"text/css"</span> />
|
||
<link rel=<span class="string">"alternate stylesheet"</span> title=<span class="string">"Zenburn"</span> href=<span class="string">"/worg/style/worg-zenburn.css"</span> type=<span class="string">"text/css"</span> />
|
||
<link rel=<span class="string">"alternate stylesheet"</span> title=<span class="string">"Classic"</span> href=<span class="string">"/worg/style/worg-classic.css"</span> type=<span class="string">"text/css"</span> />
|
||
<link rel=<span class="string">"stylesheet"</span> href=<span class="string">"http://orgmode.org/css/lightbox.css"</span> type=<span class="string">"text/css"</span> media=<span class="string">"screen"</span> /></pre><p>This is how it looks like on <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">EmacsWiki</a> pages</p><pre> <link type=<span class="string">"text/css"</span> rel=<span class="string">"stylesheet"</span> href=<span class="string">"/emacs/wiki.css"</span> /></pre><p>Note the absence of “alternate stylesheet” attributes. I am wondering whether such directives could be added to the site.</p></div><div class="color one level0"><p> Given the selection we have on the <a class="local" href="https://www.emacswiki.org/emacs/CSS">CSS</a> page, which are the themes you’d like to hard-code as alternatives? – Alex</p></div><div class="color two level0"><p> I went through the available stylesheets and moved my favorites to the top. None of them are perfect but several could potentially be fixed into something decent with a bit of tweaking. In my opinion this is a very serious issue. Applying a new CSS theme made the wiki spring to life for me. --<a class="local" href="https://www.emacswiki.org/emacs/MikeAbrahams">MikeAbrahams</a></p></div><div class="color one level0"><p> What do you guys think about updating the default theme of the site? I think it looks really nice with a lighter theme like Cali+ or <a class="url http outside" href="http://www.emacswiki.org/emacs?action=browse;bootstrap=0;id=CSS;css=/css/pedia.css">Wikipedia</a>, but the gray and orange theme is kind of dark. I’m mostly thinking of new users - it took me a couple of years to realize you could change the look of the site, but I’ve really enjoyed visiting here since discovering those other themes. – <a class="local" href="https://www.emacswiki.org/emacs/BrianBurns">BrianBurns</a></p></div><div class="color two level0"><p> I’m in favor of trying something new! – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><div class="color one level0"><p>Okay great! I put up an album of screenshots for some themes (just things that I thought might look good as a default theme, and some others) for comparison at <a class="url http" href="http://imgur.com/a/czk9D">http://imgur.com/a/czk9D</a> - I like the lighter themes but they could still use some tweaking - I’d like to try and make one that combines</p><ul><li>Made in California (gray links, but larger <code>‘function references’</code> text)</li><li>Cali+ (headings, have section separators but lighter dots, box around table of contents)</li><li>Planet CSS (code block font, colored syntax highlighting)</li><li>Wikipedia (large logo on left, maybe try a vertical sidebar)</li></ul><p>and see how it looks - other suggestions are welcome too. I’ll put the CSS on Github when I get it started - it can be a collaborative effort, and I’ll post to the dev list and reddit once I get the Github up for some more feedback.</p><p>– <a class="local" href="https://www.emacswiki.org/emacs/BrianBurns">BrianBurns</a></p></div><div class="color two level0"><p> Thanks! Looking forward to it. I just checked and it seems the current theme was added installed <a class="local" href="https://www.emacswiki.org/emacs/2013-04-24">2013-04-24</a>.</p><p>– Alex Schroeder</p></div><h2>Talk link indicates whether page already exists</h2><p>Could there be some sort of styling or tooltip to indicate if the talk page exists/has talk on it? I like to browse the talk pages to see some meta-discussion. But if it’s not there, I don’t want to bother clicking through.</p><p>On Pmwiki, Talk-links are followed by a question-mark if there is no page (it’s the default indicator that a wiki-link does not exist). I don’t actually like the question-mark. On Wikipedia… well, I can’t find an article without a talk page right now. No idea.</p><p>While I’m on about Talk, is there a reason that Talk asks for a users homepage-url, while other edits only ask for username? --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p><div class="color one level0"><p> Wikipedia makes the talk link red. <a class="url http" href="http://en.wikipedia.org/wiki/Inciting_incident">http://en.wikipedia.org/wiki/Inciting_incident</a> as of 21 September 2013 at 16:30. – Anon</p></div><div class="color two level0"><p> Sure. I think there’s a related question, here: Should all links to non-existing pages get “red link” instead of the question-mark? For now, I’ll see about a simple change that only affects the comment links we have right now…</p><p>Here’s what I’m doing right now: If the comment link points to a comment-page that doesn’t exist, the class “edit” is added but without changing it into a standard edit link (no questionmark!). Plus, if you’re using the default setup with bootstrap CSS, I’m adding the “warning” <a class="url http outside" href="http://getbootstrap.com/css/#buttons">button style</a>, resulting in a yellow button instead of a standard yellow button for non-existing Talk pages. What do you think? – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h2>Easy navigation from talk page back to parent</h2><p>Pages (“parents” or “parent pages”) have links to goto/create talk pages, but there’s no reverse functionality on the talk pages to go back to the parent (that I can see). This would be nice. --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p><div class="color one level0"><p> Do you see the link at the bottom that says <em style="text-decoration: underline; font-style: normal;">Article</em>? If so, that’s the one and perhaps it could use some further highlighting. If you don’t, then that’s a bug. – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><div class="color two level0"><div class="portrait"><p><a class="newauthor" href="https://www.emacswiki.org/emacs/MichaelPaulukonis" title="2013-05-08 13:16 UTC"><img alt="new: 2013-05-08 13:16 UTC" class="portrait" src="http://gravatar.com/avatar/2c387befb1ee085fd6706bd59efa042f" /></a> <br /> <a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><p> Ah! <strong>NOW</strong> I see it. I’d probably like both of them up top, next to the page name. When I’m on the talk page I more want to go back to the parent then to see what links to the talk page (default title-link behavior). --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><div class="color one level0"><p> What do you think of the change I just made? It moves the <em style="text-decoration: underline; font-style: normal;">Article</em> or <em style="text-decoration: underline; font-style: normal;">Talk</em> link (if any) to right after the header.</p><p>In case you’re interested, I added the following to <a class="url http outside" href="http://emacswiki.org/emacs/emacs-bootstrap.js">emacs-bootstrap.js</a>:</p><pre> // move article link and talk link below title
|
||
var $link = $('a.original').add('a.comment')<span class="comment">;</span>
|
||
if ($link) {
|
||
$('.header h1').after($('<p>').append($link))<span class="comment">;</span>
|
||
}</pre><p>– <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><div class="color two level0"><p> I don’t see it. Then again, I don’t use the bootstrap version…</p><p>I agree that the link back to the page commented on should be much more prominent. And the main page is not necessarily an “article”. It is sometimes a file in <a class="local" href="https://www.emacswiki.org/emacs/ElispArea">ElispArea</a>, for instance. – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p></div><div class="color one level0"><div class="portrait"><p><a class="newauthor" href="https://www.emacswiki.org/emacs/MichaelPaulukonis" title="2013-05-08 14:53 UTC"><img alt="new: 2013-05-08 13:16 UTC" class="portrait" src="http://gravatar.com/avatar/2c387befb1ee085fd6706bd59efa042f" /></a> <br /> <a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><p> I like it. I’m not going to say “love”, as we’ve (I) have also got the two searchboxes up there. I know, I’m being finicky; I don’t have a complete suggestion of how to better use the space. Something like how mediawiki (or the styling that wikipedia uses) displays the Article/Talk tabs, maybe?</p><p>On a related note, are there any keybindings for common functionality – like edit, talk, article/parent? That would remove part of the issue with having them below/above the fold.</p><p>I agree with Drew about the “article” issue. I usually think of everything in here as a page, anyway. [for all of my caveats, I was amazed at the response time. woooh!] --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><div class="color two level0"><p> The name “article” is just what Wikipedia uses so it is easier to understand. There are “access keys” which might work for you but I don’t know them by heart. If you use the English interface then I’d try e for edit, c for comment and a for article, perhaps? – Alex</p></div><div class="color one level0"><div class="portrait"><p><a class="newauthor" href="https://www.emacswiki.org/emacs/MichaelPaulukonis" title="2013-05-08 18:59 UTC"><img alt="new: 2013-05-08 13:16 UTC" class="portrait" src="http://gravatar.com/avatar/2c387befb1ee085fd6706bd59efa042f" /></a> <br /> <a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><p> Okay, those work. I see <strong>e</strong> is documented at <a class="local anchor" href="https://www.emacswiki.org/emacs/HowToEdit#accesskeys">HowToEdit#accesskeys</a>, and <strong>p</strong> is down below here in dialog, but there’s no central documentation of them? Where would be the best place to document ALL of these? I.E., I’ll do it. --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><div class="color two level0"><p> There is no central documentation. They just get added ad-hoc. Let me check the source. 😊</p><dl><dt>e</dt><dd>edit (German: b)</dd><dt>s</dt><dd>save</dd><dt>p</dt><dd>preview</dd><dt>f</dt><dd>find</dd><dt>a</dt><dd>article</dd><dt>c</dt><dd>comment</dd></dl><p>As for where to document them, I don’t know. Probably a new page to link from <a class="local" href="https://www.emacswiki.org/emacs/HowToEdit">HowToEdit</a>? – Alex</p></div><div class="color one level0"><div class="portrait"><p><a class="newauthor" href="https://www.emacswiki.org/emacs/MichaelPaulukonis" title="2013-05-10 18:31 UTC"><img alt="new: 2013-05-08 13:16 UTC" class="portrait" src="http://gravatar.com/avatar/2c387befb1ee085fd6706bd59efa042f" /></a> <br /> <a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><p> Say “hello!” to <a class="local" href="https://www.emacswiki.org/emacs/AccessKey">AccessKey</a> --<a class="local" href="https://www.emacswiki.org/emacs/MichaelPaulukonis">MichaelPaulukonis</a></p></div><h2>User Names on RecentChanges Page</h2><p>It would be good if user names were treated normally at <a class="local" href="https://www.emacswiki.org/emacs/RecentChanges">RecentChanges</a>, that is, to show a non-existant page like a non-existant page is usually shown. People might be encouraged to follow it and create a home page.</p><div class="color one level0"><p> I haven’t thought about this in a long time. Maybe you’re right. – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h2>Layout</h2><h3>Edit Page</h3><p>What about moving the “Please make sure…” text, plus the Username field above the text-input editing box? That would reduce the need to scroll the page by placing the Save and Preview buttons closer to the editing box (using Preview more than once while editing is common). In fact, it would be great if those two buttons could be on the same line as the “This change is a minor edit” check box, making them even closer to the edit box. – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p><div class="color one level0"><p> At the time I did this on purpose to make sure people read the blurb… :/</p><p>As for hitting Preview a lot: The access key should be P, so try M-p or C-p in your browser (see <a class="url http outside" href="http://en.wikipedia.org/wiki/Access_key#Access_in_different_browsers">this list</a> too see which modifiers are used in different browsers).</p><p>Other than that, if you have a CSS-based suggestion, we can try it out. – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h3>Keys</h3><div class="color one level0"><p> Adding some style changes to break out <code> from the surrounding text would be very helpful for key strokes. Especially if they are something like ‘<code>C-x (</code>’ which is used for starting a keyboard macro. – <a class="local" href="https://www.emacswiki.org/emacs/DocWhat">DocWhat</a></p></div><div class="color two level0"><p> Do you mean in addition to using a monospaced font, something like a light gray background? Alternatively, the weird accents-used-as-apostrophes such as <code>‘C-x C-c’</code> usually work. Unfortunately, the regular expression used prevents `C-x (’ from working. 😟</p><p>The particular regular expressions used, straight from the Perl code:</p><pre> if (/<span>\G</span>(<span>\`</span>|‘)([CM][- ][- A-Za-z0-9<><span class="comment">;:#]+)(<span>\'</span>|’)/cg</span>
|
||
or /<span>\G</span>(<span>\`</span>|‘)([-A-Za-z0-9<span>\/</span><span>\*</span>]+[=]?)(<span>\'</span>|’)/cg) {
|
||
return $q->code('&#x2018<span class="comment">;' . $2 . '&#x2019;');</span>
|
||
}</pre><p>Any suggestions for improvement? It would obviously be easy to style these occurrences. But how? – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h2>Click the heading to search for pages in this category / that link here</h2><p>This bothers me similarly to the above since it just adds clutter for anyone who knows what clicking on a header does. I would like to remove this too but this would probably not be well received. I would suggest that this information is somehow shown on all pages but in an less intrusive way.</p><p>Maybe somewhere in the footer close to where the language links are too. Then again this link (“Pages linking here”) as well as the links to the translations can easily be missed. Maybe both kinds should be placed somewhere more visible? But if you do this please do so in a way that makes it easy to hide it using a style sheet. – <a class="local" href="https://www.emacswiki.org/emacs/JonasBernoulli">JonasBernoulli</a></p><h2>Subscription service to watch changes</h2><p>There should be a way to subscribe to changes to pages of interest to users, including Emacs Lisp files.</p><div class="color one level0"><p> The current option is to subscribe to RSS feeds for each page or for pages matching a particular regular expression. The html has appropriate meta links. Alternatively you could go to <a class="local" href="https://www.emacswiki.org/emacs/RecentChanges">RecentChanges</a>, figure out what settings you need and change “action=rc” in the URL to “action=rss”.</p><p>The URL for this page, for example, would be one of these:</p><ul><li><code>http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions</code> – the default, listing the last major change in the last 7 days</li><li><code>http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;days=30</code> – listing the last major change in the last 30 days</li><li><code>http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;showedit=1</code> – listing the last change (major or minor) in the last 7 days</li><li><code>http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;full=1</code> – listing the last major change in the last 7 days with full page content (unless it’s blows the arbitrary limit I’ve set in order to save bandwidth)</li><li><code>http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;full=1;diff=1</code> – listing the last major change in the last 7 days with full page content and diff</li><li><code>http://www.emacswiki.org/emacs/?action=rss;match=emacs</code> – listing the last major change for any page matching the Perl regular expression “emacs” in the last 7 days</li></ul><p>There are many more parameters to tune this.</p><p>Finally, if a few people were interested, we could add an <em style="text-decoration: underline; font-style: normal;">email subscription</em> extension to the wiki. If you’d like to see this, edit this page and leave your name or send me an email <<a class="url mailto" href="mailto:alex@emacswiki.org">mailto:alex@emacswiki.org</a>>.</p><p>– <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h2>Email Subscription</h2><p>Leave your name here if you are interested adding a feature to <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">EmacsWiki</a> (probably as a button at the bottom of each page) to receive email alerts when a page changes.</p><ul><li><a class="local" href="https://www.emacswiki.org/emacs/PatrickAnderson">PatrickAnderson</a></li><li>xuhdev</li></ul><h2>Screenshots for major modes</h2><div class="color one level0"><p> I would like to see a screenshot showing what each mode looks like.</p><p>I just read about <a class="local" href="https://www.emacswiki.org/emacs/AllOut">AllOut</a> mode and wanted to see what it looked like; it would have been nice if there was a screenshot.</p><p>--<a class="local" href="https://www.emacswiki.org/emacs/LuisFernandes">LuisFernandes</a></p></div><div class="color two level0"><p> Yeah, technically this is possible and <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a> does it a lot for the documentation of his Icicles package. It’s a lot of work, unfortunately. – Alex</p></div><h2>Protect users with only linking to signed downloads and/or signed checksums</h2><p>The development community is a great target for peers with ill intent. And what better place to attack than the editors/IDEs that devs use to write code all the other devs use.</p><p>Whether sitting on university, coffee shop or a conference public wifi, devs often work in public spaces where the network can be compromised. Compromising wifi networks is pretty easy too these days: add one of these to a shopping cart and off you go <a class="url https" href="https://wifipineapple.com/">https://wifipineapple.com/</a></p><p>Therefore, please protect us by only offering downloads to and only linking to downloads that offer either an encrypted download or an encrypted checksum. The encryption would have to be verifiable: HTTPS is a good starting place, GPG and HTTPS hosted public keys could work too.</p><p>Here’s an example of a link that raised this concern: <a class="url http" href="http://sourceforge.net/projects/jdee/files/jdee/2.4.1/">http://sourceforge.net/projects/jdee/files/jdee/2.4.1/</a> Here’s an example of Eclipse offering secure checksums <a class="url https" href="https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz">https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz</a> offers a link to <a class="url https" href="https://www.eclipse.org/downloads/sums.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz&type=sha1">https://www.eclipse.org/downloads/sums.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz&type=sha1</a> Not ideal, but if you are in a public area you can check and then trust the download.</p><p>Many Thanks</p><p>– Anonymous</p><div class="color one level0"><p> I’m not sure <i>how</i> we should go about doing that… Check every outbound link? Scrape target websites? This is way too much work. Are you concerned only about the downloads from the <a class="local" href="https://www.emacswiki.org/emacs/ElispArea">ElispArea</a>? Anybody can come and edit the files. What additional security would encryption and checksums provide, given that there is no security at the page level?</p><p><b>If, as a user, you are concerned about the code, you must refrain from downloading source code from Emacs Wiki.</b> I would think that you should also only download code from trusted sources (and by that I mean code signed by particular people you know). This is the point where we must realize that security is not just cryptography. It’s also an open society, the ability to criticize, publish, talk, double check.</p><p><b>If, as an author, you are concerned about other people changing your code, you must refrain from uploading source code to Emacs Wiki.</b></p><p>Perhaps the download button should carry a warning? Then again, perhaps every page should carry a warning… But, if every page carries a warning, it means nothing. Thus I’d argue that the status quo is good enough. Visitors know that <b>a wiki implies a lack of security</b>.</p><p>– <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><div class="color two level0"><p> A parenthetical remark concerning my libraries: As an Emacs-Wiki administrator, I lock the wiki pages for the code I upload, so you can be pretty sure that it has not been tampered with. – <a class="local" href="https://www.emacswiki.org/emacs/DrewAdams">DrewAdams</a></p></div><h2>Instant Answers for DuckDuckGo</h2><p>Emacs Wiki relies on <a class="local" href="https://www.emacswiki.org/emacs/DuckDuckGo">DuckDuckGo</a> for in-site search. Maybe develop a <a class="url https outside" href="https://duck.co/ia">DuckDuckGo instant answer</a> such that each time when <a class="local" href="https://www.emacswiki.org/emacs/EmacsWiki">EmacsWiki</a> updates, the changes in <a class="local" href="https://www.emacswiki.org/emacs/DuckDuckGo">DuckDuckGo</a>’s search results are updated instantly?</p><div class="color one level0"><p> How is that going to work? The way I see it, an Instant Answer can take a search query and produce an answer using code and data – but what we would like is <i>push</i> page edits so that <a class="local" href="https://www.emacswiki.org/emacs/DuckDuckGo">DuckDuckGo</a> updates their index, right? Or am I misunderstanding something? – <a class="local" href="https://www.emacswiki.org/emacs/AlexSchroeder">AlexSchroeder</a></p></div><h2>Changing default font to sans-serif</h2><p>In conformity to the many other application wikis out there, the emacs wiki should at least use a sans-serif font as default across its pages.</p><p>Many other application wikis use a sans serif font, not to mention Wikipedia itself. Some examples include <a class="url https outside" href="https://wiki.archlinux.org/index.php/Arch_Linux">Arch</a> and <a class="url https outside" href="https://en.wiktionary.org/wiki/Wiktionary:Main_Page">Wikitionary</a>.</p><div class="color one level0"><p> There’s a <a class="url https outside" href="https://github.com/bburns/emacswiki-light-theme">github repo</a> for the new css, so I think that it would be better to place your suggestion there. Personally, though, I don’t agree and I think that looking like the other wikis out there is not a goal. But I’ll leave it to the author of the theme we’re using. Also note that you can use your own <a class="local" href="https://www.emacswiki.org/emacs/CSS">CSS</a>. Perhaps you want that <a class="url https outside" href="https://www.emacswiki.org/emacs?action=browse;id=CSS;css=/css/pedia.css">Wikipedia theme</a>?</p><p>– Alex Schroeder</p></div><h2>Add "random" button to sidebar</h2><p><a class="url http number" href="http://www.emacswiki.org/emacs/?action=random"><span><span class="bracket">[</span>4<span class="bracket">]</span></span></a> is a pretty neat tool, it would be nice to just be able to click it from the side bar.</p><p>--Billy</p><div class="color one level0"><p> There was actually such a link in the side bar, a very long time ago. I no longer remember why it got removed. Probably somebody said it didn’t serve any purpose. – Alex</p><p>– Greg</p><p>Please update this page <a class="url https" href="https://www.emacswiki.org/emacs/MsWindowsGlobalContextMenu">https://www.emacswiki.org/emacs/MsWindowsGlobalContextMenu</a> to correct the section referencing C:\Documents and Settings\yourName\<a class="local" href="https://www.emacswiki.org/emacs/SendTo">SendTo</a></p><p>This is now located at C:\Users\USERNAME\<a class="local" href="https://www.emacswiki.org/emacs/AppData">AppData</a>\Roaming\Microsoft\Windows\<a class="local" href="https://www.emacswiki.org/emacs/SendTo">SendTo</a></p></div><hr /><p><a class="local" href="https://www.emacswiki.org/emacs/CategoryEmacsWikiSite">CategoryEmacsWikiSite</a></p></div><div class="wrapper close"></div></div><footer><hr /><span class="translation bar"><br /> <a class="translation de" href="https://www.emacswiki.org/emacs/Gnu">Deutsch</a> <a class="translation new" href="https://www.emacswiki.org/emacs?action=translate;id=EmacsWikiSuggestions;missing=es_fr_it_ja_ko_pt_ru_se_uk_zh" rel="nofollow">Add Translation</a></span><div class="edit bar"><a accesskey="c" class="comment local" href="https://www.emacswiki.org/emacs/Comments_on_EmacsWikiSuggestions">Talk</a> <a accesskey="e" class="edit" href="https://www.emacswiki.org/emacs?action=edit;id=EmacsWikiSuggestions" rel="nofollow" title="Click to edit this page">Edit this page</a> <a class="history" href="https://www.emacswiki.org/emacs?action=history;id=EmacsWikiSuggestions" rel="nofollow">View other revisions</a> <a class="admin" href="https://www.emacswiki.org/emacs?action=admin;id=EmacsWikiSuggestions" rel="nofollow">Administration</a></div><div class="time">Last edited 2022-01-12 19:30 UTC by <span class="ip-code" title="Anonymous"><span class="orange">1</span><span class="blue">4</span><span class="violet">6</span><span class="orange">1</span></span> <a class="diff" href="https://www.emacswiki.org/emacs?action=browse;diff=2;id=EmacsWikiSuggestions" rel="nofollow">(diff)</a></div><div style="float:right; margin-left:1ex;">
|
||
<!-- Creative Commons License -->
|
||
<a class="licence" href="https://creativecommons.org/licenses/GPL/2.0/"><img alt="CC-GNU GPL" style="border:none" src="/pics/cc-GPL-a.png" /></a>
|
||
<!-- /Creative Commons License -->
|
||
</div>
|
||
|
||
<!--
|
||
<rdf:RDF xmlns="http://web.resource.org/cc/"
|
||
xmlns:dc="http://purl.org/dc/elements/1.1/"
|
||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
|
||
<Work rdf:about="">
|
||
<license rdf:resource="https://creativecommons.org/licenses/GPL/2.0/" />
|
||
<dc:type rdf:resource="http://purl.org/dc/dcmitype/Software" />
|
||
</Work>
|
||
|
||
<License rdf:about="https://creativecommons.org/licenses/GPL/2.0/">
|
||
<permits rdf:resource="http://web.resource.org/cc/Reproduction" />
|
||
<permits rdf:resource="http://web.resource.org/cc/Distribution" />
|
||
<requires rdf:resource="http://web.resource.org/cc/Notice" />
|
||
<permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" />
|
||
<requires rdf:resource="http://web.resource.org/cc/ShareAlike" />
|
||
<requires rdf:resource="http://web.resource.org/cc/SourceCode" />
|
||
</License>
|
||
</rdf:RDF>
|
||
-->
|
||
|
||
<p class="legal">
|
||
This work is licensed to you under version 2 of the
|
||
<a href="https://www.gnu.org/">GNU</a> <a href="/GPL">General Public License</a>.
|
||
Alternatively, you may choose to receive this work under any other
|
||
license that grants the right to use, copy, modify, and/or distribute
|
||
the work, as long as that license imposes the restriction that
|
||
derivative works have to grant the same rights and impose the same
|
||
restriction. For example, you may choose to receive this work under
|
||
the
|
||
<a href="https://www.gnu.org/">GNU</a>
|
||
<a href="/FDL">Free Documentation License</a>, the
|
||
<a href="https://creativecommons.org/">CreativeCommons</a>
|
||
<a href="https://creativecommons.org/licenses/sa/1.0/">ShareAlike</a>
|
||
License, the XEmacs manual license, or
|
||
<a href="/OLD">similar licenses</a>.
|
||
</p>
|
||
<p class="legal" style="padding-top: 0.5em">Please note our <a href="/emacs/Privacy">Privacy Statement</a>.</p>
|
||
</footer>
|
||
</body>
|
||
</html>
|