August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: selection or font problem 24 years, 8 months

Jan Vroonhof

Stef Epardaud <stef(a)lunatech.com> writes: > Jan Vroonhof said it could be my font, but then ... isn't xemacs > supposed to handle different fonts ? especially the one it gets for > 'default' ? I am not saying it isn't a bug. I just think that it might get triggered by the font you have: > http://tanglefoot.lunatech.com/~stephane/xemacs-sel2.gif Notice how in your case the highlighted line touches the "t", whereas for me it doesn't Jan

4 participants
7 comments

Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly hard/undocumented?) 24 years, 8 months

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: ... > I have every reason to understand (and I agree with) your other goals; > but what's wrong with catering to people who have enough disk space > that they'd rather waste a few dozen MB rather than tell their fingers > NOT to go "(tar xvzf ...; ./configure; make; make install)"? First, until ETL *I* haven't had the disk space to do this.[1] Now that I'm at ETL and have disk space, I don't have bandwidth for uploading to the FTP site. I was told four months ago that I would be able to carve out an area on the local FTP server for XEmacs tarballs, but it still hasn't happened yet. Footnotes: [1] Which shouldn't have stopped someone who did from doing it, but that did not happen either.

1 participants
0 comments

Re: [SITE] make over finished(?) 24 years, 8 months

SL Baur

john s anderson <jacobs(a)azstarnet.com> writes in xemacs-beta(a)xemacs.org: > Ok, let me re-phrase the question: > Is it useful or desirable to make a distinction between packages that are > somewhat officially sanctioned by virtue of being in the Sumo Tarballs and > in the package indexes (e.g., Gnus) and those that are available as binary > packages by other means (e.g., x-symbol). I don't think so, at least to the "officially sanctioned" part. Packages not in the Sumos need to be noted so people know about them, but that doesn't make them any less sanctioned. The packages not in the Sumos are there because they potentially conflict with other packages and we haven't worked out conflict resolution yet. I hope this explanation makes the distinction clearer.

1 participants
0 comments

Re: problem w/ toggle-auto-compression in 21.1.6? 24 years, 8 months

Jan Vroonhof

"Charles Hines" <chuck_hines(a)vnet.ibm.com> writes: > (1) (initialization/error) An error has occurred while loading ~/.emacs: > > Symbol's value as variable is void: file-coding-system-alist See http://www.xemacs.org/list-archives/xemacs-patches/9908/msg00013.html Jan

2 participants
1 comments

problem w/ toggle-auto-compression in 21.1.6? 24 years, 8 months

Charles Hines

Howdy all. Sorry if this has already been brought up (lately I don't/can't pay as much attention to the list as I would like to) but has anyone noticed that if you try and run toggle-auto-compression on that 21.1.6 complains about file-coding-system-alist as being non-existent: (1) (initialization/error) An error has occurred while loading ~/.emacs: Symbol's value as variable is void: file-coding-system-alist Compiled on AIX 4.1.5, no mule, jka-compr from sumo tarball from 7/30. Version 21.1.3 with the 5/30 sumo tarball worked fine, BTW. Thanks, Chuck -- Charles K. Hines <chuck_hines(a)vnet.ibm.com> <hinesc(a)us.ibm.com> IBM Logic Synthesis Developer [BooleDozer (TM)] Martial Arts Instructor [Modern Arnis and Balintawak Escrima] "Go back to sleep, Chuck. You're just havin' a nightmare -- of course, we ARE still in Hell." (Gary Larson)

1 participants
0 comments

Re: [SITE] make over finished(?) 24 years, 8 months

Jan Vroonhof

john s anderson <jacobs(a)azstarnet.com> writes: > Ok, let me re-phrase the question: > Is it useful or desirable to make a distinction between packages that are > somewhat officially sanctioned by virtue of being in the Sumo Tarballs and > in the package indexes (e.g., Gnus) and those that are available as binary > packages by other means (e.g., x-symbol). Maybe for practical reasons (i.e. that for packages of the Gnus type people can simply visit there friendly local List & Install). I don't consider the "officially sanctioned" part that important. Jan

1 participants
0 comments

RE: Layout support + widget fixes 24 years, 8 months

Damon Lipparelli

Under WinNT, using MSVC, the link fails with: glyphs-widget.obj : error LNK2005: _Qlayout already defined in general.obj ..\src\temacs.exe : fatal error LNK1169: one or more multiply defined symbols found Under Solaris 2.5.1, using GCC 2.95.1, compilation fails with: toolbar-x.c: In function `x_draw_blank_toolbar_button': toolbar-x.c:81: too many arguments to function `x_output_shadows' toolbar-x.c: In function `x_output_toolbar_button': toolbar-x.c:163: too many arguments to function `x_output_shadows' toolbar-x.c:217: warning: passing arg 11 of `x_output_x_pixmap' makes integer from pointer without a cast toolbar-x.c:217: too few arguments to function `x_output_x_pixmap' -lipp -----Original Message----- From: Andy Piper [mailto:andy＠xemacs.org] Sent: Monday, August 23, 1999 9:40 AM To: xemacs-patches(a)xemacs.org Cc: xemacs-beta(a)xemacs.org Subject: Layout support + widget fixes This allows you to layout glyphs according to some predefined strategy within a predefined area, e.g. right justified. You can optionally draw a border round the layout area which can be etched in/out or bevelled in/out. Layouts can be organised within layouts allowing for arbitrarily complex structures. My calculations tell me that if you put a border round sub-layouts you can get a nice table effect (which might interest BillP). This is based on the stuff Ben wrote up in architecting XEmacs, the bugs are all my own. This also fixes a whole bunch of bugs in the subwindow support. I intend applying this tomorrow morning GMT unless 21.2.20 is imminent. andy 1999-08-23 Andy Piper <andy(a)xemacs.org> * event-Xt.c (emacs_Xt_handle_magic_event): use find_matching_subwindow to check whether the exposure is totally inside a subwindow, if it is then ignore it. * glyphs.c (find_matching_subwindow): new function. * gutter-items.el (update-tab-in-gutter): call add-tab-to-gutter here if we don't have one. * toolbar-x.c (x_draw_blank_toolbar_button): use new x_output_shadows signature. (x_output_toolbar_button): use new x_output_x_pixmap signature. * redisplay.h (struct display_box): new structure. (struct display_glyph_area): ditto. declare new display_box functions. * redisplay-x.c (x_output_pixmap): update for new display box stuff. (x_bevel_area): update to allow multiple edge styles and border segments. (x_output_display_block): update for new display_box stuff and signatures. (x_clear_region): ditto. (x_output_x_pixmap): ditto. adjust offsets rather than clip. (console_type_create_redisplay_x): declare new console methods. (x_output_vertical_divider): update for new bevel_area signature. (x_output_shadows): update to allow selective drawing of edges. * redisplay-tty.c (tty_output_display_block): do nothing for layouts. * redisplay-output.c (redisplay_output_subwindow): convert to use display_box structure, this allows us to put subwindows anywhere with any offset, useful for layout glyphs. (redisplay_output_layout): new function. output a layout and its sub-glyphs. (redisplay_output_pixmap): new modular function combining generic parts of the X and mswindows versions. convert to use display_box structures. (redisplay_clear_clipped_region): new function. clear the area a glyph is going into. (redisplay_normalize_glyph_area): new function. calculate the bounds of a display_glyph_area given a display_box. (redisplay_normalize_display_box): new function. shrink a display_box to enclose a display_glyph_area. (redisplay_display_boxes_in_window_p): check whether the input display_box and display_glyph_area are actually in a window. (redisplay_calculate_display_boxes): calculate display boxes based on conventional display_line metrics. (bevel_modeline): update for new bevel_area signature. * redisplay-msw.c (mswindows_output_blank): update for new display_box stuff. (mswindows_output_string): ditto. (mswindows_output_dibitmap): ditto. (mswindows_output_dibitmap_region): ditto. (mswindows_output_pixmap): ditto. (mswindows_bevel_area): update to allow multiple edge styles and border segments. (mswindows_output_display_block): update for new display_box stuff and signatures. (mswindows_clear_region): ditto. (console_type_create_redisplay_mswindows): declare new console methods. * lisp.h (edge_style): new enum. declare display_box and display_glyph_area. * gutter.c (output_gutter): update for new bevel_area signature. * glyphs.h (image_instance_type): add layout. (IMAGE_LAYOUT_MASK): ditto. (LAYOUT_IMAGE_INSTANCEP): new macro. (CHECK_LAYOUT_IMAGE_INSTANCE): ditto. (struct Lisp_Image_Instance): add offsets for layout and the layout type itself. move mask here also. (IMAGE_INSTANCE_LAYOUT_CHILDREN): new macro. (IMAGE_INSTANCE_LAYOUT_BORDER): ditto. (XIMAGE_INSTANCE_LAYOUT_CHILDREN): ditto. (XIMAGE_INSTANCE_LAYOUT_BORDER): ditto. * glyphs.c (mark_image_instance): update for layouts. (print_image_instance): ditto. (image_instance_equal): ditto. (image_instance_hash): ditto. (allocate_image_instance): initialise offsets for layout. (decode_image_instance_type): update for layouts. (encode_image_instance_type): ditto. (Fimage_instance_height): ditto. (Fimage_instance_width): ditto. (allocate_glyph): ditto. (glyph_width): allow image instances as an argument. update for layouts. (glyph_height_internal): ditto. (syms_of_glyphs): add layout symbols. * glyphs-x.h (struct x_image_instance_data): remove mask entry. (IMAGE_INSTANCE_X_MASK): update. * glyphs-x.c (x_label_instantiate): new function. instantiate a label. (image_instantiator_format_create_glyphs_x): initialise new layout glyph type. * glyphs-widget.c: new layout type. (check_valid_orientation): new keyword checker for layouts. (check_valid_justification): ditto. (check_valid_border): ditto. (check_valid_glyph_or_image_list): ditto. (layout_possible_dest_types): new function for layout glyph type. (layout_normalize): ditto. (layout_instantiate): ditto. (syms_of_glyphs_widget): new keywords for layout. (image_instantiator_format_create_glyphs_widget): initialise the layout glyph type. * glyphs-msw.h (struct mswindows_image_instance_data): remove mask argument. (IMAGE_INSTANCE_MSWINDOWS_MASK): update. * glyphs-msw.c: declare layout format. (image_instantiator_format_create_glyphs_mswindows): initialise it. * general.c: new symbols for layouts. * console.h (struct console_methods): new console methods for outputting pixmaps and strings. * lwlib-Xm.c (xm_create_label_field): new function for creating labels. (xm_creation_table): use it. * lwlib-Xaw.c (xaw_create_label_field): new function for creating labels. (xaw_creation_table): use it.

1 participants
0 comments

Re: [SITE] make over finished(?) 24 years, 8 months

Jan Vroonhof

john s anderson <jacobs(a)azstarnet.com> writes: > > I think it might be good to make a clear distinction between the XEmacs > > packages (i.e. the things you can install using M-x > > package-admin-add-binary-package) and the more loosely defined "Elisp > > addons". > > Right. I was planning on three sections: 'bundled' packages, 'seperate' > packages, and 'add-ons'. Of course, those last two are a bit fuzzy - would > anyone care to suggest a distinction? Like it said, I would prefer using the name "package" only for stuff that is recognised by the XEmacs package scanning code, i.e. can be installed using package-admin-add-binary-package. Jan

2 participants
1 comments

Question: How do we create links in Xemacs ? 24 years, 8 months

Vipin Menon

Hi, Could you please tell me how I can create links in Xemacs? Example: I would like to create the following text: 1. Topic 1 2. Topic 2. 3. Topic 3 This paragraph describes the material mentioned briefly in Topic 1. jrwhfjrhhgrkhjk lkrejhkrjhgkrojg bdhfgbjrebgjregknkfnm................. This paragraph describes the material mentioned briefly in Topic 2. jrwhfjrhhgrkhjk lkrejhkrjhgkrojg bdhfgbjrebgjregknkfnm................... This paragraph describes the material mentioned briefly in Topic 3. jrwhfjrhhgrkhjk lkrejhkrjhgkrojg bdhfgbjrebgjregknkfnm................... Clicking on "1. Topic 1" would move the cursor to the corresponding paragraph. Thanks in advance , Vipin -- --------------------------------------------------------- Vipin S. Menon email : vipmenon(a)spk.hp.com Hewlett Packard Company, phone : (509)921-3896 Spokane Division fax : (509)921-3991 24001 E Mission Avenue, Liberty Lake, WA 99019-9599 ---------------------------------------------------------

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 24 years, 8 months

Jan Vroonhof

Ulrich Drepper <drepper(a)cygnus.com> writes: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > > > Ok, if you want you can remove the debug message. Not finding the > > input context is not going to hurt. > > OK, but aren't there resource problems? Do these windows still exist > though they are not used? Yes. But they are reused when you have new windows with scrollbars. Jan

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 August 1999