November 2014 - XEmacs-Beta - XEmacs Mailing List Archives

Some questions about wrapping types 9 years, 11 months

Johann 'Myrkraverk' Oskarsson

Hi all, First, I'm asking for some advice and/or thoughts. Even so, I may decide to do something completely different after reading all the replies. You have been warned. For reference, I've been working on a libClang wrapper. I already have a little more than a hello-world already, and have wrapped three types, and implemented a few functions that return and use these types. What's currently bothering me, is how to handle a type like CXCursor, http://clang.llvm.org/doxygen/structCXCursor.html which is not completely opaque. (Opaque types are rather easy). First of all, I believe it'll be beneficial to be able to (get cursor 'kind) and possibly (get cursor 'xdata) which is an integer. However, there is also a documented void * in it. This void pointer is kind of "bothering" me. I can quite easily return nil from (get cursor 'data) and I can also signal an error. Are there any other sane options? For the record, for now, (put cursor ...) and (remprop cursor ...) are not supported; and never may be. As in, trying to use them results in an error. On the other hand (object-plist cursor) isn't even implemented, and I have no idea what to do with it. Any ideas? Also, the (get cursor 'kind) returns another type, which I've not yet wrapped. This is an enumerator documented at http://clang.llvm.org/doxygen/group__CINDEX.html#gaaccc432245b4cd9f2d4709... and I wonder what some options are to represent this in elisp? My first thought is to represent it as symbols (possibly even keywords). Another would be to create yet another type and create constants. This can potentially also be done with integers. Any comments on the pros and cons of the various options? So far, I don't have enough experience with the libClang interface to actually form an opinion. I may even decide to try a few options and see which feels best. That's it for now, Johann _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
10 comments

module-directory is nil with -batch? (21.4.22) 9 years, 11 months

Johann 'Myrkraverk' Oskarsson

Hi all, The following command displays nil, $ xemacs -batch -eval '(message "%s" module-directory)' nil is that a bug? This is 21.4.22 and -vanilla changes nothing. The OS is illumos (solaris) and I built xemacs myself. Furtermore, on Ubuntu, I get /build/buildd/xemacs21-21.4.22/modules/ which is probably incorrect. Is that a bug for the package maintainer? Does anyone have an explanation for the difference? Johann _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
6 comments

keybinding puzzle 9 years, 11 months

Julian Bradfield

I don't understand the following, in any XEmacs: Suppose I get a buffer, and switch on quail, using, say, chinese-tonepy. If I do C-h b , the output starts with Minor Mode Bindings for `quail-mode': key binding --- ------- .. ~ quail-start-translation .. ÿ quail-start-translation Local Bindings: ......... The first range of keys starts with SPC (or at least, that's a SPC at the start of the line). Doing a map-keymap to print the bindings in quail-mode-map also shows a binding of SPC to quail-start-translation. Yet if I do C-h k SPC , I'm told that SPC is bound to self-insert-command ; and (lookup-key quail-mode-map ?\ ) tells me there's no binding of SPC there. Can somebody explain what's happening here? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
1 comments

startup: xemacs wants to create a directory 9 years, 12 months

Uwe Brauer

Hello When I closed xemacs in my last session I had a file open in a directory which does not exist anymore, however I now obtain on start up the directory foo does not exist, Create? And independent what I answer next time I start this message still pops up, this is annoying, which package could cause such a behaviour? Thanks Uwe Brauer _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

Summary of XEmacs Issue Tracking System Issues 9 years, 12 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2014-11-18 - 2014-11-25) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 563 open ( +0) / 317 closed ( +0) / 880 total ( +0) Open issues with patches: 13 Average duration of open issues: 1923 days. Median duration of open issues: 2089 days. Open Issues Breakdown new 255 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 58 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

The proper way to refer and document types in docstrings? 10 years

Johann 'Myrkraverk' Oskarsson

Hi all, Is there a convention to refer to and document types in docstrings? I'm asking because I'm creating a binding with an emodule, and have to create several new types. (I already know the basics of how to do this). The first "module" I thought to check was postgresql, but it doesn't actually document its types. If I put something like `my-type' in a docstring, do people expect to be able to find a docstring with something like C-h v ? And related; is there something people typically use to jump from a docstring to a related info manual? -- Johann, where he admits his ignorance of docstring usage. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Highlighting a face? 10 years

Johann 'Myrkraverk' Oskarsson

Hi all, I've been wondering, is there a different way to say "boldface" than to inherit bold? Currently I'm doing this in my init.el: (set-face-property 'font-lock-variable-name-face 'highlight [bold highlight]) The lispref itself seems silent on what the allowed values for this property are. If I understand correctly, the bold face highlight is a specifier with specific values for a TTY and an X frame; so most of the time I'd want to just use that. On the other hand, it seems the lispref is lacking and I'm curious if there are other ways to do it. Johann _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
3 comments

bugs in edit-last-kbd-macro 10 years

Julian Bradfield

I tried to use this function (having very rarely done so in the past), and found not one but two silly bugs in it. (With just updated packages.) To reproduce, get a buffer and put the text here is some text with <foo> and junk in it. Move to beginning, and: C-x ( C-s <foobar> RET C-x ) M-x edit-last-kbd-macro RET C-c C-c The edit will fail, because the editing buffer says Key: none and none is not a valid key specification. If one solves this by assigning it to a key, then the edit still fails, because the main body of the editing buffer is Macro: C-s ;; isearch-forward <foo> ;; self-insert-command * 5 RET ;; newline and on edit <foo> is read as a key specification for a non-existent key. Should be treating < as a special character and putting a space after it, or whatever it does. Does somebody know the code well enough to fix it quickly, or should I? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

XEmacs Packages have been pre-released (2014-11-18-20) 10 years

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== cc-mode-1.84-pkg.tar.gz upstream version: 5.32.5 Previously Announced Packages Still in Pre-Release: ================================================== ada-1.16-pkg.tar.gz upstream version: 2.27 apel-1.36-pkg.tar.gz upstream version: 10.7 auctex-1.54-pkg.tar.gz upstream version: 11.84 bbdb-1.34-pkg.tar.gz upstream version: 2.35 build-1.17-pkg.tar.gz upstream version: 2.02 c-support-1.24-pkg.tar.gz upstream version: none calc-1.28-pkg.tar.gz upstream version: 2.02fX3 cedet-common-1.03-pkg.tar.gz upstream version: 1.0pre4 clearcase-1.12-pkg.tar.gz upstream version: /main/laptop/165 cogre-1.04-pkg.tar.gz upstream version: 0.5 cookie-1.17-pkg.tar.gz upstream version: none crisp-1.17-pkg.tar.gz upstream version: 1.34 debug-1.20-pkg.tar.gz upstream version: none dictionary-1.18-pkg.tar.gz upstream version: 1.8 dired-1.22-pkg.tar.gz upstream version: 7.17 docbookide-0.10-pkg.tar.gz upstream version: 0.1 easypg-1.05-pkg.tar.gz upstream version: 0.0.16 ecb-1.25-pkg.tar.gz upstream version: 2.31 ecrypto-0.23-pkg.tar.gz upstream version: 2.0 ede-1.06-pkg.tar.gz upstream version: 1.0pre4 edebug-1.24-pkg.tar.gz upstream version: none edict-1.19-pkg.tar.gz upstream version: 0.9.9 ediff-1.84-pkg.tar.gz upstream version: 2.75 edt-1.16-pkg.tar.gz upstream version: none efs-1.37-pkg.tar.gz upstream version: 1.24 egg-its-1.29-pkg.tar.gz upstream version: none eieio-1.09-pkg.tar.gz upstream version: 1.0pre4 elib-1.15-pkg.tar.gz upstream version: 1.0 emerge-1.13-pkg.tar.gz upstream version: none erc-0.26-pkg.tar.gz upstream version: Version 5.1.2 Revision: 1.796.2.6 escreen-1.03-pkg.tar.gz upstream version: 1.16 eshell-1.20-pkg.tar.gz upstream version: 0fc80a3f6bb3bb59f42e9ff83cc8b89bf90fe658 ess-1.18-pkg.tar.gz upstream version: 5.2.7 eterm-1.20-pkg.tar.gz upstream version: none eudc-1.43-pkg.tar.gz upstream version: 1.32 footnote-1.18-pkg.tar.gz upstream version: 0.18x forms-1.17-pkg.tar.gz upstream version: 2.37 fortran-modes-1.07-pkg.tar.gz upstream version: none frame-icon-1.13-pkg.tar.gz upstream version: none fsf-compat-1.24-pkg.tar.gz upstream version: none games-1.23-pkg.tar.gz upstream version: 2.00 general-docs-1.08-pkg.tar.gz upstream version: none gnats-1.19-pkg.tar.gz upstream version: 3.101 guided-tour-0.54-pkg.tar.gz upstream version: none haskell-mode-1.14-pkg.tar.gz upstream version: 2.1 hm--html-menus-1.26-pkg.tar.gz upstream version: 5.9 hyperbole-1.22-pkg.tar.gz upstream version: 5.0.5 ibuffer-1.12-pkg.tar.gz upstream version: none idlwave-1.34-pkg.tar.gz upstream version: 5.1 igrep-1.18-pkg.tar.gz upstream version: 2.111 ilisp-1.38-pkg.tar.gz upstream version: 5.12.0 ispell-1.37-pkg.tar.gz upstream version: 3.6 jde-1.54-pkg.tar.gz upstream version: 2.3.5.1 latin-euro-standards-1.11-pkg.tar.gz upstream version: 1.11 latin-unity-1.23-pkg.tar.gz upstream version: 1.23 leim-1.38-pkg.tar.gz upstream version: none locale-1.30-pkg.tar.gz upstream version: none lookup-1.17-pkg.tar.gz upstream version: 1.0 mail-lib-1.83-pkg.tar.gz upstream version: none mailcrypt-2.16-pkg.tar.gz upstream version: 3.5.8 mh-e-1.35-pkg.tar.gz upstream version: 7.4.2 mine-1.18-pkg.tar.gz upstream version: 1.9 misc-games-1.25-pkg.tar.gz upstream version: none mmm-mode-1.08-pkg.tar.gz upstream version: 0.4.8 mule-base-1.60-pkg.tar.gz upstream version: none mule-ucs-1.21-pkg.tar.gz upstream version: 0.84 ocaml-0.10-pkg.tar.gz upstream version: 3.06 oo-browser-1.07-pkg.tar.gz upstream version: 4.08 os-utils-1.44-pkg.tar.gz upstream version: none pc-1.30-pkg.tar.gz upstream version: none pcl-cvs-1.73-pkg.tar.gz upstream version: R-2_9_9 pcomplete-1.08-pkg.tar.gz upstream version: 1.1.6 perl-modes-1.16-pkg.tar.gz upstream version: none pgg-1.10-pkg.tar.gz upstream version: 0.1 prog-modes-2.31-pkg.tar.gz upstream version: none ps-print-1.14-pkg.tar.gz upstream version: 6.5.6 psgml-1.49-pkg.tar.gz upstream version: 1.3.2 psgml-dtds-1.05-pkg.tar.gz upstream version: none python-modes-1.16-pkg.tar.gz upstream version: 5.0.0 re-builder-1.07-pkg.tar.gz upstream version: 1.20 reftex-1.36-pkg.tar.gz upstream version: 4.21 riece-1.26-pkg.tar.gz upstream version: 3.1.2 rmail-1.16-pkg.tar.gz upstream version: none ruby-modes-1.07-pkg.tar.gz upstream version: 1.8.7 sasl-1.18-pkg.tar.gz upstream version: 1.14.4 scheme-1.22-pkg.tar.gz upstream version: none semantic-1.23-pkg.tar.gz upstream version: 2.0pre4 sgml-1.13-pkg.tar.gz upstream version: none sh-script-1.26-pkg.tar.gz upstream version: 2.0f sieve-1.20-pkg.tar.gz upstream version: none skk-1.27-pkg.tar.gz upstream version: 10.62a slider-1.18-pkg.tar.gz upstream version: 0.3x1 sml-mode-0.14-pkg.tar.gz upstream version: 3.9.5 sounds-au-1.14-pkg.tar.gz upstream version: none sounds-wav-1.14-pkg.tar.gz upstream version: none speedbar-1.32-pkg.tar.gz upstream version: 1.0pre4 strokes-1.12-pkg.tar.gz upstream version: none supercite-1.23-pkg.tar.gz upstream version: 3.55x3 texinfo-1.32-pkg.tar.gz upstream version: none text-modes-2.05-pkg.tar.gz upstream version: none textools-1.17-pkg.tar.gz upstream version: none time-1.16-pkg.tar.gz upstream version: 1.17 tm-1.42-pkg.tar.gz upstream version: none tooltalk-1.17-pkg.tar.gz upstream version: none tpu-1.16-pkg.tar.gz upstream version: 4.2X tramp-1.52-pkg.tar.gz upstream version: 2.2.10 vc-1.50-pkg.tar.gz upstream version: none vc-cc-1.24-pkg.tar.gz upstream version: none vhdl-1.24-pkg.tar.gz upstream version: 3.33.12 view-process-1.15-pkg.tar.gz upstream version: 2.4 viper-1.69-pkg.tar.gz upstream version: 3.09 vm-8.11-pkg.tar.gz upstream version: 8.0.12-devo w3-1.41-pkg.tar.gz upstream version: 4.0pre47 x-symbol-1.16-pkg.tar.gz upstream version: 4.5.1 xemacs-base-2.43-pkg.tar.gz upstream version: none xemacs-devel-1.84-pkg.tar.gz upstream version: none xetla-1.04-pkg.tar.gz upstream version: steve(a)eicq.org--2005/xetla--main--1.1--version-0 xlib-1.16-pkg.tar.gz upstream version: lg(a)xwem.org--2005/xlib--main--2.1--version-0 xslide-1.11-pkg.tar.gz upstream version: 0.2.2 xslt-process-1.14-pkg.tar.gz upstream version: 1.2.1 xwem-1.25-pkg.tar.gz upstream version: lg(a)xwem.org--2005/xwem--main--2.1--versionfix-1 zenirc-1.18-pkg.tar.gz upstream version: 2.112 Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/cc-mode/ChangeLog ------- 2014-11-18 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.84 released. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFUbO247yJLt8ORD7cRAgKlAJ4nu/PhTQwZpYUu4wTsJr3ko/Bz+QCgi93+ mpUWWiFZYk3YHqxPrpnJeWs= =i8KE -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Doc(?) bugs in 21.4 (lispref, CCL) 10 years

Aidan Kehoe

Ar an triú lá de mí na Samhain, scríobh Johann 'Myrkraverk' Oskarsson: > [...] > > > And in the context of changing the lispref, is it within the scope of > > > a bugfix to include usage examples for these functions (if I can come > > > up with simple ones)? > > > > For XEmacs 21.5, IMHO the criterion for doc changes is not "is it a > > bugfix", but "is the change likely to confuse users". > > > > For XEmacs 21.4, I suspect that Vin would take usage examples if and > > only if they accompany a bugfix in the docs, but it's entirely up to > > him. > > Ok. Everything I'm doing about the lispref also seems to apply to > 21.5 too - this section is identical. > > I personally don't care if examples never make it to the lispref, I > can always just put them on my blog. It's the erroneous and > misleading docs that I care about. I’m enthusiastic about (your :) fixing the docs in 21.4, and applying the same changes to 21.5. I include docstrings in “docs”. I don’t think that there’s enough of a win for changing code when that code change is not a clear bugfix. > I'm going to give people a few days to reply to any points I've > touched upon, before I start to write any more change proposals. -- ‘Tramadol is further fed to cattle […] when working them […] (as draft animals) so that the animals do not get tired quickly. …’ — Angewandte Chemie, Sept 2014, describing the social context of (synthetic) tramadol having been found in Cameroon tree roots. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta November 2014