Hi all,
I've recently started building with clang, which indeed does give
nicer error messages than GCC (at least up to GCC v4.4). However, it
also gives an annoying warning about the extensible struct idiom:
struct Lisp_Vector {
NORMAL_LISP_OBJECT_HEADER header;
long size;
Lisp_Object contents[1];
}
where we allocate a larger buffer to hold our Lisp_Vector, then
populate contents[] with more objects than it is declared to hold.
Like this:
------------------------------------------------------------------------------
/playpen/src/XEmacs/xemacs/src/frame.c:2903:28: warning: array index of '1' indexes past the end of an array (that contains 1 elements) [-Warray-bounds]
Lisp_Object face_prop = XVECTOR_DATA (prop)[1];
^ ~
In file included from /playpen/src/XEmacs/xemacs/src/frame.c:366:
/playpen/src/XEmacs/xemacs/src/lisp.h:2709:25: note: instantiated from:
#define XVECTOR_DATA(s) vector_data (XVECTOR (s))
^
/playpen/src/XEmacs/xemacs/src/lisp.h:2708:24: note: instantiated from:
#define vector_data(v) ((v)->contents)
^
/playpen/src/XEmacs/xemacs/src/lisp.h:2695:15: note: array 'contents' declared here
Lisp_Object contents[1];
^
------------------------------------------------------------------------------
Is there an idiom for this that won't offend clang? Or should I turn
off -Warray-bounds for clang?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
I am trying to switch from Matlab to Octave and
octave-mode.el allows me to use it from Xemacs; I already
contacted the maintainers about the following problem, but
did not receive any feedback so far. The problem is
connected with the shell buffer in Xemacs.
In the so called inferior octave mode
I use the help
command, say help deconv I obtain
help deconv
WARNING: terminal is not fully functional^M
^M- (press RETURN)
And the whole *Octave Inferior* buffer is un usable. I
presume it has to do with the fact that the "shell" command
is using a simplified terminal. I tried to do the same by
not starting the octave inferior shell but
M-x shell
octave
help deconv
And got the same result.
Then I tried
M-x term
but this is much worse the prompt is distorted and when I
executed octave *nothing* happened.
Anybody can help?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Uwe Brauer writes:
> >> On Fri, 21 Oct 2011 12:14:57 +0200, Giacomo Boffi <giacomo.boffi(a)polimi.it> wrote:
>
> > i should have been drunken... no need to go through the shell alias,
> > just do
> > echo '(setenv "PAGER" "cat")' >> ~/.xemacs/init.el
> > once for all
>
> Oops you want to set shell code in the lisp file?
no, i want to modify the environment that xemacs passes to its
subprocesses
----------------------------------------------------------------------
(describe-function 'setenv)
`setenv' is an interactive compiled Lisp function
-- loaded from ".../xemacs/lisp/process.elc"
(setenv VARIABLE &optional VALUE UNSET SUBSTITUTE-ENV-VARS)
Documentation:
Set the value of the environment variable named VARIABLE to VALUE.
VARIABLE should be a string. VALUE is optional; if not provided or is
`nil', the environment variable VARIABLE will be removed.
UNSET, if non-nil, means to remove VARIABLE from the environment.
SUBSTITUTE-ENV-VARS, if non-nil, means to substitute environment
variables in VALUE using `substitute-env-vars'.
Interactively, a prefix argument means to unset the variable.
Interactively, the current value (if any) of the variable
appears at the front of the history list when you type in the new value.
This function works by modifying `process-environment'.
As a special case, setting variable `TZ' calls `set-time-zone-rule' as
a side-effect.
Invoked with:
M-x setenv
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Stephen J. Turnbull writes:
> I don't think that's a good idea, at least until Norbert has/we have a
> good feel for when "multiple heads" happens. Maybe Norbert just needs
> to update first.
In this case, since he's committed already, updating to the other head
will do the Wrong Thing. So he should just merge and then push.
But in the future, I think that (a) for Norbert "hg pull -u" should
DTRT, and (b) if multiple heads happen anyway and it's not obvious why
(ie, another package maintainer committed a new patch before Norbert
could respond to the first one, in which case pull and merge == hg
fetch *is* the right thing), we need to figure out why.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
My son Byrel and I have made three programs that we want to make into
packages for distributing with the XEmacs packaging system: an easy way
to change buffer colors, an implementation of icon themes, and thirdly,
a CNC major mode with a lot of code(200k?) for editing CNC G-code
machine files for different machine tools.
He'll be home from grad school for a bit next month and I am trying to
get things ready so we can make and upload the packages then.
I can find descriptions of the package system, how to use it to update
your packages etc, but I am not finding a step by step list of
directions to make some lisp code and some documentation into a package.
Is there such a list, and if not, where do I go to learn how to make a
package?
I would appreciate any advice, or pointers to documentation that anyone
can give.
Also, is there an approval/review process for packages?
Assuming I get them made in some way or another, where is it appropriate
to upload them? I don't think I have write access to anything that I
know of and expect I won't get everything right the first time around.
Steve Mitchell
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-10-11 - 2011-10-18)
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.
533 open ( +1) / 274 closed ( +0) / 807 total ( +1)
Open issues with patches: 11
Average duration of open issues: 937 days.
Median duration of open issues: 986 days.
Open Issues Breakdown
new 210 ( +1)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 150 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
Issues Created Or Reopened (1)
______________________________
broken link: _ELSE_ in Download/elispPackages 2011-10-12
http://tracker.xemacs.org/XEmacs/its/issue809 created stephen
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
We've been getting our source-code repo services from Alioth; its
service has deteriorated to the point of making a move necessary: So,
from now on, the "master" repositories for XEmacs and its packages will
reside on Bitbucket. We're taking this opportunity to also move the
packages from CVS on Alioth to Mercurial on Bitbucket.
Here's what you need to know:
* Pointing your existing XEmacs repo at bitbucket
In your existing repo, edit .hg/hgrc to contain this:
[paths]
default = https://bitbucket.org/xemacs/xemacs
If you have commit access, you should use:
[paths]
default = ssh://hg@bitbucket.org/xemacs/xemacs
* Checking out a fresh XEmacs repo
Do this:
hg clone https://bitbucket.org/xemacs/xemacs
or, if you have commit access:
hg clone ssh://hg@bitbucket.org/xemacs/xemacs
* Checking out the packages
Do this:
hg clone https://bitbucket.org/xemacs/xemacs-packages
or, if you have commit access:
hg clone ssh://hg@bitbucket.org/xemacs/xemacs-packages
Note: You need at least Mercurial 1.3 for this, preferably a later
version, as all the individual packages reside in subrepositories.
* Getting push access
Get an account on bitbucket.org. Send e-mail to Mike Sperber
<mike(a)xemacs.org> informing him of the account name, and what exactly
you need access for.
* Notes on the packages subrepositories
The packages repository is organized as the xemacs-packages "master"
repository and one subrepository per package. This means that each
revision of xemacs-packages contains references to specific revisions of
the subrepositories. More info on subrepositories is available as the
output of "hg help subrepos" or here:
http://mercurial.selenic.com/wiki/Subrepository
If you're working on an individual package, just run "hg commit" *within
the directory of that package* and also run "hg push" from there. Then
tell Norbert Koch <viteno(a)xemacs.org> about it (as usual), who will
make sure that the set of packages referenced from "xemacs-packages" is
consistent and push from there.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Raymond Toy <toy.raymond(a)gmail.com> writes:
> On Sun, Oct 9, 2011 at 6:30 AM, Michael Sperber <sperber(a)deinprogramm.de>wrote:
>
>>
>>
>> What's your version of Mercurial? Can you send the output of
>>
>
> hg --version says 1.4.3. FWIW, I was able to check the packages on a couple
> of other machines which were using newer versions of hg (> 1.6, I think).
Then I think we can safely blame 1.4 as a too-old version, right?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta