From: Nikola Skoric <nick-news@net4u.hr>
To: help-gnu-emacs@gnu.org
Subject: Re: deleting minibuffer
Date: Wed, 29 Aug 2007 16:42:55 +0000 (UTC) [thread overview]
Message-ID: <fb47mf$ima$1@ss408.t-com.hr> (raw)
In-Reply-To: m27ine4c1k.fsf@cochabamba.cs.uu.nl
Dana Wed, 29 Aug 2007 17:04:39 +0200,
Piet van Oostrum <piet@cs.uu.nl> kaze:
>>>>>> Nikola Skoric <nick-news@net4u.hr> (NS) wrote:
>
>>NS> Hi there everybody :-) I'm a brand new emacs user, and I'd like to get
>>NS> rid of some of some minibuffers that I generate (for instance
>>NS> *Completions* minibuffer) and then the y get in my way when I do the
>>NS> C-x -> thing. When I do C-x 0, I get "Attempt to delete minibuffer...".
>>NS> Why is attempting to delete minibuffer wrong?
>
> *Completions* is not a minibuffer. The minibuffer is on the bottom of the
> frame (window) and is usually only one line high. It is used for additional
> input to commands, e.g. file names. Without minibuffer Emacs cannot
> function properly. However, the *Completions* can be deleted without
> problems. I don't know what you mean with the C-x -> thing.
When I have more than one buffer opened, then I go to next buffer with C-x, and
then right arrow. If I have, say, 2 buffers opened, and then use completion, a
3. buffer gets opened. If I go to that buffer, and press C-x 0, I get "Attempt
to delete minibuffer or sole ordinary window". How do I get rid of that buffer?
>>NS> Second thing is: how do I force emacs to break lines for me? When I write
>>NS> news posts, I want my lines to be less than 70 chars. Is there a way to
>>NS> force emacs to break my lines for me?
>
> menu: Options -> Word wrap in text modes. Don't forget to select Options ->
> Save Options if you want to keep it the same for fututre Emacs sessions.
> The value 70 can be set by customizing fill-column. Use Options ->
> Customize Emacs -> Specific Options and specify fill-column in the
> minibuffer.
> You can then fill in the value 70 in the dialog window and save it for
> future session with the appropriate button.
Thank you very much! :-)
--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"
next prev parent reply other threads:[~2007-08-29 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 11:19 deleting minibuffer Nikola Skoric
2007-08-29 12:29 ` sunway
2007-08-29 13:25 ` Nikola Skoric
2007-08-29 13:44 ` Peter Dyballa
2007-08-29 15:04 ` Piet van Oostrum
2007-08-29 16:42 ` Nikola Skoric [this message]
2007-08-29 17:42 ` Malte Spiess
2007-08-29 18:25 ` Nikola Skoric
2007-08-29 19:01 ` Peter Dyballa
2007-08-30 21:38 ` roodwriter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fb47mf$ima$1@ss408.t-com.hr' \
--to=nick-news@net4u.hr \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).