Talk:Awesome

From ArchWiki
Jump to: navigation, search

Add a new solution in "Troubleshooting" (4.9)

Grammar/spelling looks okay apart from the first sentence (Once installed...), but I'd leave it out anyway, as redundant.

About the content, /usr/share/X11/xkb/compat/basic is owned by extra/xkeyboard-config, and not in its backup array, so this will get undone on upgrades. -- Alad (talk) 12:44, 23 March 2016 (UTC)

Originally or after an upgrade, you are probably faced this problem. -- Like this? :-) first sentence. Thank you, Alad! -- Vladimir Shatalin (talk) 19:19, March 23, 2016

Mouse does not work in non-Latin keyboard layout

In English, please check (grammar and spelling): Once installed, the Awesome, or after an upgrade, you are probably faced this problem. The mouse does not work in non-Latin keyboard layout (for example, in Russian keyboard, mouse clicks are not processed by tags, and you can not call the Awesome menu). See this bug for details. To resolve this problem, edit the file /usr/share/X11/xkb/compat/basic, and comment out (using //) in these lines there, as shown below:

 // Group 2 = AltGr;
 // Group 3 = AltGr;
 // Group 4 = AltGr;

Русский: Сразу после установки Awesome, или после обновления системы, вы вероятно сталкивались с такой проблемой. Мышка не работает в не латинской раскладке клавиатуры (например при Русской раскладки клавиатуры, щелчки мышью по тэгам не обрабатываются, также вы не можете вызвать меню Awesome). Смотрите подробно об этой ошибке. Для решения этой проблемы, отредактируйте файл /usr/share/X11/xkb/compat/basic, и закомментируйте (при помощи //) в нём эти строки, как указано ниже:

//group 2 = AltGr;
//group 3 = AltGr;
//group 4 = AltGr;

-- Vladimir Shatalin (talk) 18:12, March 23, 2016

KDM is depracated.

It's best to replace it with instructions for SDDM. Dillebidum (talk) 10:16, 28 November 2016 (UTC)

Awesome wiki links broke?

Jasper1984 (talk) 00:20, 14 January 2017 (UTC)

Awesome wiki is offline, they are going to document everything within ldoc. See https://github.com/awesomeWM/awesome-www/issues/7 Martin92 (talk)

Prepare for Awesome4

Once Awesome4 is packaged for Arch the wiki should be updated immediately. According to their Porting-tips the upgrade will break users existing config (depending on what they did), so it would be nice to have an paragraph about porting (or at least a link to their porting tips). Im new to the Archwiki but I guess it would be worth to create a new "awesome4" page and redirect "awesome" to "awesome4" in time? Martin92 (talk)

Ive created a stub: awesome4 Martin92 (talk)

Since Arch only supports the latest package versions, creating a new page for a new version is pointless. Please update the information on this page instead. -- Alad (talk) 16:15, 15 January 2017 (UTC)
Do you mean in the spirit of an "Awesome4"-Section that is then replacing the main section in time? Martin92 (talk) 16:48, 15 January 2017 (UTC)
I see 2 options here:
  • A (easier):
    1. Create a new "Awesome 4" section here;
    2. Expand the section with the awesome 4 changes;
    3. When awesome 4 is released, properly and progressively merge it in the rest of the article.
  • B (tidier):
    1. Protect this article from further edits (admin);
    2. Create a temporary User:Martin92/Awesome 4 page;
    3. Copy 1:1 the current content of this article there;
    4. Add a notice at the top of this article to explain the reason for the protection and point possible contributors to the temporary article (admin);
    5. Adapt the content of the temporary page to version 4, properly and progressively;
    6. When awesome 4 is released, merge the temporary article here (admin).
Kynikos (talk) 09:40, 16 January 2017 (UTC)
Why not rather point to the official documentation?
-- Ambrevar (talk) 08:31, 23 January 2017 (UTC)
I think those links will do the job, but Awesome 4 has been released in Community meanwhile, so if the article needs updating it can be done on the spot, without following the procedure above. – Kynikos (talk) 10:14, 24 January 2017 (UTC)

Randomized Wallpaper Script Recfactor

I would like to propose a slight edit/addition to the linked lua script here. As is, math.random will use the same number repeatedly. To fix this, math.randomseed(os.time) should proceed this.

According to lua documentation, "The math.randomseed() function sets a seed for the pseudo-random generator..."

I've tested this solution, and it appears to be working.