EmacsWikiSuggestions

Thanks for asking before just doing it. Yes, I object.

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).

I don’t object to removal of some how-to information that could no longer be used by anyone.

The point is that this site is about Emacs, not only GnuEmacs, 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 (CategoryHistory), and pages about the GNU/XEmacs split (EmacsSchism, EmacsAndXEmacs, EmacsSchismDiscussion).

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.

Just one opinion.

FWIW - I agree with all that Alex has said. – DrewAdams

No, I don’t think so. I added Log4E Logging For Elisp to CategoryDebug. – DrewAdams

There’s a github repo for the new css, so I think that it would be better to place your suggestion there. I created a new issue just for that.

I think a syntax like ^EmacsWiki to automatically generate a link with spacing like Emacs Wiki 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.

--MikeAbrahams

I wonder whether I understood this correctly. You can always create link to pages containing spaces using double square brackets [[Like This]]. And we should totally encourage people to do that, and to redirect from pages LikeThis to pages [[Like This]]. Are you arguing that typing ^LikeThis is much easier than [[Like This]] or were you unaware of the double square bracket syntax, or did I miss something? – Alex Schroeder

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.

(I’ve updated HowTo to mention page CSS.) – DrewAdams

Given the selection we have on the CSS page, which are the themes you’d like to hard-code as alternatives? – Alex

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 Wikipedia, 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. – BrianBurns

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 http://imgur.com/a/czk9D - I like the lighter themes but they could still use some tweaking - I’d like to try and make one that combines

• Made in California (gray links, but larger ‘function references’ text)
• Cali+ (headings, have section separators but lighter dots, box around table of contents)
• Planet CSS (code block font, colored syntax highlighting)
• Wikipedia (large logo on left, maybe try a vertical sidebar)

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.

– BrianBurns

Wikipedia makes the talk link red. http://en.wikipedia.org/wiki/Inciting_incident as of 21 September 2013 at 16:30. – Anon

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

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));
  }

– AlexSchroeder

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

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

Say “hello!” to AccessKey --MichaelPaulukonis

I haven’t thought about this in a long time. Maybe you’re right. – AlexSchroeder

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 (see this list too see which modifiers are used in different browsers).

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

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 days
• http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;days=30 – listing the last major change in the last 30 days
• http://www.emacswiki.org/emacs?action=rss;rcidonly=EmacsWikiSuggestions;showedit=1 – listing the last change (major or minor) in the last 7 days
• http://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 diff
• http://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 days

There 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>.

– AlexSchroeder

I would like to see a screenshot showing what each mode looks like.

I just read about AllOut mode and wanted to see what it looked like; it would have been nice if there was a screenshot.

--LuisFernandes

I’m not sure how 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 ElispArea? 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?

If, as a user, you are concerned about the code, you must refrain from downloading source code from Emacs Wiki. 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.

If, as an author, you are concerned about other people changing your code, you must refrain from uploading source code to Emacs Wiki.

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 a wiki implies a lack of security.

– AlexSchroeder

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 push page edits so that DuckDuckGo updates their index, right? Or am I misunderstanding something? – AlexSchroeder

There’s a github repo 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 CSS. Perhaps you want that Wikipedia theme?

– Alex Schroeder

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

– Greg

Please update this page https://www.emacswiki.org/emacs/MsWindowsGlobalContextMenu to correct the section referencing C:\Documents and Settings\yourName\SendTo

This is now located at C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\SendTo