From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xah Newsgroups: gmane.emacs.help Subject: Emacsw32 website suggestion [Re: Behavior of M-x and A-x] Date: Tue, 12 Aug 2008 06:06:54 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <9cb65794-fa18-4a0e-9a82-27e85923038a@v26g2000prm.googlegroups.com> <857a6a64-0971-495b-aad8-1c069405e13e@i20g2000prf.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1218548499 5869 80.91.229.12 (12 Aug 2008 13:41:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Aug 2008 13:41:39 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Aug 12 15:42:30 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KSu8W-0004r8-5g for geh-help-gnu-emacs@m.gmane.org; Tue, 12 Aug 2008 15:42:08 +0200 Original-Received: from localhost ([127.0.0.1]:40098 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KSu7a-0002iR-0h for geh-help-gnu-emacs@m.gmane.org; Tue, 12 Aug 2008 09:41:10 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!w1g2000prk.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 106 Original-NNTP-Posting-Host: 24.6.97.120 Original-X-Trace: posting.google.com 1218546415 26050 127.0.0.1 (12 Aug 2008 13:06:55 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 12 Aug 2008 13:06:55 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: w1g2000prk.googlegroups.com; posting-host=24.6.97.120; posting-account=bRPKjQoAAACxZsR8_VPXCX27T2YcsyMA User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.2 Safari/525.22, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:161163 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:56508 Archived-At: On Aug 12, 5:13 am, "Lennart Borgman (gmail)" wrote: > Xahwrote: > >Xahwrote: > >> ; setting the PC keyboard's various keys to Super or Hyper > >> (setq w32-pass-lwindow-to-system nil > >> w32-pass-rwindow-to-system nil > >> w32-pass-apps-to-system nil > >> w32-lwindow-modifier 'super ;; Left Windows key > >> w32-rwindow-modifier 'super ;; Right Windows key > >> w32-apps-modifier 'hyper) ;; Menu key > > > Lennart Borgman wrote: > > >> Please note that using lwindow/rwindow like this does not work for all > >> key sequences unless you are using the patched Emacs+EmacsW32. > > > What is the proper way to set it on Windows? > > The only thing that the patched version really offers in this regards is > the possibility to actually avoid sending lwindow etc to the system: > > LRESULT > CALLBACK > LowLevelKeyboardProc(INT nCode, WPARAM wParam, LPARAM lParam) > { > ... > case VK_LWIN: > { > bHandle =3D NILP(Vw32_pass_lwindow_to_system); > break; > } > case VK_RWIN: > { > bHandle =3D NILP(Vw32_pass_rwindow_to_system); > break; > } > case VK_CAPITAL: > { > bHandle =3D NILP(Vw32_enable_caps_lock); > break; > } > case VK_NUMLOCK: > { > bHandle =3D NILP(Vw32_enable_num_lock); > break; > } > case VK_MENU: > case VK_LMENU: > case VK_RMENU: > { > bHandle =3D NILP(Vw32_pass_alt_to_system); > break; > } > if (bHandle) { > // Just to be sure check we are in the right thread > if (GetCurrentThreadId() =3D=3D dwWindowsThreadId) { > // Do we have keyboard focus? > HWND hwnd =3D GetFocus(); > if (0 !=3D hwnd) { > SendMessage (hwnd, msg, wParamMsg, lParamMsg); > return TRUE; > } > } > } > } > HHOOK hhook; return CallNextHookEx(hhook, nCode, wParam, lParam); > > } > > And then it also offers easy way to set things up up, see w32-meta.el > that comes with the patched Emacs+EmacsW32. Thanks. Quite complicated i don't understand. That seems c source. ------------- there's some suggestion about your emacsw32 site. =E2=80=A2 drop the name to just EmacsW32. As opposed to Emacs+EmacsW32. for those who needs to know the distinction, they can trivially find out by clicking a link. =E2=80=A2 redo the entry page so it's simply a site for EmacsW32, as a pre- compiled emacs distro for MS Windows. With this message simple. Then links to separate pages about features, source code, explanation of patch, on reason to use, change log, etc. The point is that, when user goes to your site, http://ourcomments.org/Emacs/EmacsW32.html she can immediately get the idea that this is a pre-compiled emacs distro for Windows with ease to use in mind. Then, she can click on the big download button to try it out. If she's a tech geeker, she can easily check whether there's patch she can dowload, or other info. Aquamac or Carbon Emacs' website are good examples of this approach. =E2=80=A2 Put the author name in the front page. Unless for some personal reason, you intentionally don't want people to know who made it, it should have author name. Xah =E2=88=91 http://xahlee.org/ =E2=98=84