Dernière modification
Résumé : signed my vandalism
Ajouté(e) :
> --MichaelPaulukonis
This page is for recording (or discussion) of Suggestions about the EmacsWiki Web site.
If you want to record or discuss problems with the Web site (not with Emacs), please do so at EmacsWikiProblems.
Make sure your suggestion doesn’t exist already or that your question has already been answered by checking the HowTo and WikiQuestions pages, respectively.
Discussion about the front page of the Wiki is at SiteMap Discussion.
Discussion about the table of contents at the top of each page is at TableOfContentsDiscussion.
Discussion about the “Goto Bar”, the links at the top and bottom of each page, is at GotoBarDiscussion.
Discussion about the TextFormattingRules used in contributing to pages is at TextFormattingDiscussion.
Add your suggestions below this line.
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.
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.
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?
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. --MichaelPaulukonis
Do you see the link at the bottom that says Article? If so, that’s the one and perhaps it could use some further highlighting. If you don’t, then that’s a bug. – AlexSchroeder
Ah! NOW 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). --MichaelPaulukonis
What do you think of the change I just made? It moves the Article or Talk link (if any) to right after the header.
In case you’re interested, I added the following to emacs-bootstrap.js:
// move article link and talk link below title
var $link = $('a.original').add('a.comment');
if ($link) {
$('.header h1').after($('<p>').append($link));
}I don’t see it. Then again, I don’t use the bootstrap version…
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 ElispArea, for instance. – DrewAdams
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?
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.
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!] --MichaelPaulukonis
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
Okay, those work. I see e is documented at HowToEdit#accesskeys, and p 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. --MichaelPaulukonis
There is no central documentation. They just get added ad-hoc. Let me check the source. :)
As for where to document them, I don’t know. Probably a new page to link from HowToEdit? – Alex
Say “hello!” to AccessKey --MichaelPaulukonis
I would like to choose the stylesheet for EmacsWiki easily. If Emacswiki could provide alternate stylesheets—see Worg—then I will be able to choose the theme using View->Page Style->etc menu in Firefox. – [[115.241.16.57?]]
Does CSS 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.
This is how the directives on Worg looks like:
<link rel="stylesheet" title="Standard" href="/worg/style/worg.css" type="text/css" /> <link rel="alternate stylesheet" title="Zenburn" href="/worg/style/worg-zenburn.css" type="text/css" /> <link rel="alternate stylesheet" title="Classic" href="/worg/style/worg-classic.css" type="text/css" /> <link rel="stylesheet" href="http://orgmode.org/css/lightbox.css" type="text/css" media="screen" />
This is how it looks like on EmacsWiki pages
<link type="text/css" rel="stylesheet" href="/emacs/wiki.css" />
Note the absence of “alternate stylesheet” attributes. I am wondering whether such directives could be added to the site.
Given the selection we have on the CSS page, which are the themes you’d like to hard-code as alternatives? – Alex
It would be good if user names were treated normally at RecentChanges, 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.
I haven’t thought about this in a long time. Maybe you’re right. – AlexSchroeder
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. – DrewAdams
At the time I did this on purpose to make sure people read the blurb… :/
As for hitting Preview a lot: The access key should be P, so try M-p or C-p in your browser.
Other than that, if you have a CSS-based suggestion, we can try it out. – AlexSchroeder
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 ‘C-x (’ which is used for starting a keyboard macro. – DocWhat?
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 ‘C-x C-c’ usually work. Unfortunately, the regular expression used prevents `C-x (’ from working. :(
The particular regular expressions used, straight from the Perl code:
if (/\G(\`|‘)([CM][- ][- A-Za-z0-9<>;:#]+)(\'|’)/cg or /\G(\`|‘)([-A-Za-z0-9\/\*]+[=]?)(\'|’)/cg) { return $q->code('‘' . $2 . '’'); }
Any suggestions for improvement? It would obviously be easy to style these occurrences. But how? – AlexSchroeder
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.
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. – JonasBernoulli
There should be a way to subscribe to changes to pages of interest to users, including Emacs Lisp files.
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 RecentChanges, figure out what settings you need and change “action=rc” in the URL to “action=rss”.
The URL for this page, for example, would be one of these:
http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions – the default, listing the last major change in the last 7 dayshttp://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;days=30 – listing the last major change in the last 30 dayshttp://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;showedit=1 – listing the last change (major or minor) in the last 7 dayshttp://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;full=1 – 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)http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;full=1;diff=1 – listing the last major change in the last 7 days with full page content and diffhttp://www.emacswiki.org/emacs/?action=rss;match=emacs – listing the last major change for any page matching the Perl regular expression “emacs” in the last 7 daysThere are many more parameters to tune this.
Finally, if a few people were interested, we could add an email subscription extension to the wiki. If you’d like to see this, edit this page and leave your name or send me an email <mailto:alex@emacswiki.org>.